Evaluation of documentation of a system or portion thereof

ABSTRACT

A method for execution by an analysis unit includes: obtaining a collection of data for an evaluation of documentation of a system aspect of a system; acquiring data analysis parameters regarding the evaluation of the documentation of the system aspect; determining one or more evaluation perspectives based on the data analysis parameters; determining one or more evaluation modalities based on the data analysis parameters; and evaluating the collection of data with respect to the documentation of the system aspect based on the one or more evaluation perspectives and the one or more evaluation modalities to produce one or more evaluation outputs regarding the documentation of the system aspect.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present U.S. Utility patent application claims priority pursuant to35 U.S.C. § 120 as a continuation of U.S. Utility application Ser. No.17/350,113, entitled “EVALUATION OF POLICIES OF A SYSTEM OR PORTIONTHEREOF”, filed Jun. 17, 2021, which is a continuation of U.S. Utilityapplication Ser. No. 17/128,509, entitled “EVALUATION RATING OF A SYSTEMOR PORTION THEREOF,” filed Dec. 21, 2020, which claims priority pursuantto 35 U.S.C. § 119(e) to U.S. Provisional Application No. 62/992,661,entitled “SYSTEM ANALYSIS SYSTEM”, filed Mar. 20, 2020, all of which arehereby incorporated herein by reference in their entirety and made partof the present U.S. Utility patent Application for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not Applicable.

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

Not Applicable.

BACKGROUND OF THE INVENTION Technical Field of the Invention

This disclosure relates to computer systems and more particularly toevaluation of a system.

Description of Related Art

The structure and operation of the Internet and other publicly availablenetworks are well known and support computer systems (systems) ofmultitudes of companies, organizations, and individuals. A typicalsystem includes networking equipment, end point devices such as computerservers, user computers, storage devices, printing devices, securitydevices, and point of service devices, among other types of devices. Thenetworking equipment includes routers, switches, edge devices, wirelessaccess points, and other types of communication devices that intercouplein a wired or wireless fashion. The networking equipment facilitates thecreation of one or more networks that are tasked to service all or aportion of a company's communication needs, e.g., Wide Area Networks,Local Area Networks, Virtual Private Networks, etc.

Each device within a system includes hardware components and softwarecomponents. Hardware components degrade over time and eventually areincapable of performing their intended functions. Software componentsmust be updated regularly to ensure their proper functionality. Somesoftware components are simply replaced by newer and better softwareeven though they remain operational within a system.

Many companies and larger organizations have their own InformationTechnology (IT) departments. Others outsource their IT needs to thirdparty providers. The knowledge requirements for servicing a systemtypically outstrip the abilities of the IT department or third-partyprovider. Thus, hardware and software may not be functioning properlyand can adversely affect the overall system.

Cyber-attacks are initiated by individuals or entities with the badintent of stealing sensitive information such as login/passwordinformation, stealing proprietary information such as trade secrets orimportant new technology, interfering with the operation of a system,and/or holding the system hostage until a ransom is paid, among otherimproper purposes. A single cyber-attack can make a large systeminoperable and cost the system owner many millions of dollars to restoreand remedy.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a networkedenvironment that includes systems coupled to an analysis system inaccordance with the present disclosure;

FIGS. 2A-2D are schematic block diagrams of embodiments of a computingdevice in accordance with the present disclosure;

FIGS. 3A-3E are schematic block diagrams of embodiments of a computingentity in accordance with the present disclosure;

FIG. 4 is a schematic block diagram of another embodiment of a networkedenvironment that includes a system coupled to an analysis system inaccordance with the present disclosure;

FIG. 5 is a schematic block diagram of another embodiment of a networkedenvironment that includes a system coupled to an analysis system inaccordance with the present disclosure;

FIG. 6 is a schematic block diagram of another embodiment of a networkedenvironment that includes a system coupled to an analysis system inaccordance with the present disclosure;

FIG. 7 is a schematic block diagram of another embodiment of a networkedenvironment that includes a system coupled to an analysis system inaccordance with the present disclosure;

FIG. 8 is a schematic block diagram of another embodiment of a networkedenvironment having a system that includes a plurality of system elementsin accordance with the present disclosure;

FIG. 9 is a schematic block diagram of an example of a system section ofa system selected for evaluation in accordance with the presentdisclosure;

FIG. 10 is a schematic block diagram of another example of a systemsection of a system selected for evaluation in accordance with thepresent disclosure;

FIG. 11 is a schematic block diagram of an embodiment of a networkedenvironment having a system that includes a plurality of system assetscoupled to an analysis system in accordance with the present disclosure;

FIG. 12 is a schematic block diagram of an embodiment of a system thatincludes a plurality of physical assets coupled to an analysis system inaccordance with the present disclosure;

FIG. 13 is a schematic block diagram of another embodiment of anetworked environment having a system that includes a plurality ofsystem assets coupled to an analysis system in accordance with thepresent disclosure;

FIG. 14 is a schematic block diagram of another embodiment of a systemthat includes a plurality of physical assets coupled to an analysissystem in accordance with the present disclosure;

FIG. 15 is a schematic block diagram of another embodiment of a systemthat includes a plurality of physical assets coupled to an analysissystem in accordance with the present disclosure;

FIG. 16 is a schematic block diagram of another embodiment of a systemthat includes a plurality of physical assets in accordance with thepresent disclosure;

FIG. 17 is a schematic block diagram of an embodiment of a usercomputing device in accordance with the present disclosure;

FIG. 18 is a schematic block diagram of an embodiment of a server inaccordance with the present disclosure;

FIG. 19 is a schematic block diagram of another embodiment of anetworked environment having a system that includes a plurality ofsystem functions coupled to an analysis system in accordance with thepresent disclosure;

FIG. 20 is a schematic block diagram of another embodiment of a systemthat includes divisions, departments, and groups in accordance with thepresent disclosure;

FIG. 21 is a schematic block diagram of another embodiment of a systemthat includes divisions and departments, which include system elementsin accordance with the present disclosure;

FIG. 22 is a schematic block diagram of another embodiment of a divisionof a system having departments, which include system elements inaccordance with the present disclosure;

FIG. 23 is a schematic block diagram of another embodiment of anetworked environment having a system that includes a plurality ofsecurity functions coupled to an analysis system in accordance with thepresent disclosure;

FIG. 24 is a schematic block diagram of an embodiment an engineeringdepartment of a division that reports to a corporate department of asystem in accordance with the present disclosure;

FIG. 25 is a schematic block diagram of an example of an analysis systemevaluating a system element under test of a system in accordance withthe present disclosure;

FIG. 26 is a schematic block diagram of another example of an analysissystem evaluating a system element under test of a system in accordancewith the present disclosure;

FIG. 27 is a schematic block diagram of another example of an analysissystem evaluating a system element under test of a system in accordancewith the present disclosure;

FIG. 28 is a schematic block diagram of another example of an analysissystem evaluating a system element under test of a system in accordancewith the present disclosure;

FIG. 29 is a schematic block diagram of an example of the functioning ofan analysis system evaluating a system element under test of a system inaccordance with the present disclosure;

FIG. 30 is a schematic block diagram of another example of thefunctioning of an analysis system evaluating a system element under testof a system in accordance with the present disclosure;

FIG. 31 is a diagram of an example of evaluation options of an analysissystem for evaluating a system element under test of a system inaccordance with the present disclosure;

FIG. 32 is a diagram of another example of evaluation options of ananalysis system for evaluating a system element under test of a systemin accordance with the present disclosure;

FIG. 33 is a diagram of another example of evaluation options of ananalysis system for evaluating a system element under test of a systemin accordance with the present disclosure;

FIG. 34 is a diagram of another example of evaluation options of ananalysis system for evaluating a system element under test of a systemin accordance with the present disclosure;

FIG. 35 is a schematic block diagram of an embodiment of an analysissystem coupled to a system in accordance with the present disclosure;

FIG. 36 is a schematic block diagram of an embodiment of a portion of ananalysis system coupled to a system in accordance with the presentdisclosure;

FIG. 37 is a schematic block diagram of another embodiment of a portionof an analysis system coupled to a system in accordance with the presentdisclosure;

FIG. 38 is a schematic block diagram of an embodiment of a dataextraction module of an analysis system coupled to a system inaccordance with the present disclosure;

FIG. 39 is a schematic block diagram of another embodiment of ananalysis system coupled to a system in accordance with the presentdisclosure;

FIG. 40 is a schematic block diagram of another embodiment of ananalysis system coupled to a system in accordance with the presentdisclosure;

FIG. 41 is a schematic block diagram of an embodiment of a data analysismodule of an analysis system in accordance with the present disclosure;

FIG. 42 is a schematic block diagram of an embodiment of an analyze andscore module of an analysis system in accordance with the presentdisclosure;

FIG. 43 is a diagram of an example of system aspects, evaluationaspects, evaluation rating metrics, and analysis system output optionsof an analysis system for analyzing a section of a system in accordancewith the present disclosure;

FIG. 44 is a diagram of another example of system aspects, evaluationaspects, evaluation rating metrics, and analysis system output optionsof an analysis system for analyzing a section of a system in accordancewith the present disclosure;

FIG. 45 is a diagram of an example of an identification evaluationcategory, sub-categories, and sub-sub-categories of the evaluationaspects and in accordance with the present disclosure;

FIG. 46 is a diagram of an example of a protect evaluation category,sub-categories, and sub-sub-categories of the evaluation aspects and inaccordance with the present disclosure;

FIG. 47 is a diagram of an example of a detect evaluation category,sub-categories, and sub-sub-categories of the evaluation aspects and inaccordance with the present disclosure;

FIG. 48 is a diagram of an example of a respond evaluation category,sub-categories, and sub-sub-categories of the evaluation aspects and inaccordance with the present disclosure;

FIG. 49 is a diagram of an example of a recover evaluation category,sub-categories, and sub-sub-categories of the evaluation aspects and inaccordance with the present disclosure;

FIG. 50 is a diagram of a specific example of system aspects, evaluationaspects, evaluation rating metrics, and analysis system output optionsof an analysis system for analyzing a section of a system in accordancewith the present disclosure;

FIG. 51 is a diagram of another specific example of system aspects,evaluation aspects, evaluation rating metrics, and analysis systemoutput options of an analysis system for analyzing a section of a systemin accordance with the present disclosure;

FIG. 52 is a diagram of another specific example of system aspects,evaluation aspects, evaluation rating metrics, and analysis systemoutput options of an analysis system for analyzing a section of a systemin accordance with the present disclosure;

FIG. 53 is a diagram of another specific example of system aspects,evaluation aspects, evaluation rating metrics, and analysis systemoutput options of an analysis system for analyzing a section of a systemin accordance with the present disclosure;

FIG. 54 is a diagram of another specific example of system aspects,evaluation aspects, evaluation rating metrics, and analysis systemoutput options of an analysis system for analyzing a section of a systemin accordance with the present disclosure;

FIG. 55 is a diagram of another specific example of system aspects,evaluation aspects, evaluation rating metrics, and analysis systemoutput options of an analysis system for analyzing a section of a systemin accordance with the present disclosure;

FIG. 56 is a diagram of another specific example of system aspects,evaluation aspects, evaluation rating metrics, and analysis systemoutput options of an analysis system for analyzing a section of a systemin accordance with the present disclosure;

FIG. 57 is a diagram of an example of identifying deficiencies andauto-corrections by an analysis system analyzing a section of a systemin accordance with the present disclosure;

FIG. 58 is a schematic block diagram of an embodiment of an evaluationprocessing module of an analysis system in accordance with the presentdisclosure;

FIG. 59 is a state diagram of an example of an analysis system analyzinga section of a system in accordance with the present disclosure;

FIG. 60 is a logic diagram of an example of an analysis system analyzinga section of a system in accordance with the present disclosure;

FIG. 61 is a logic diagram of another example of an analysis systemanalyzing a section of a system in accordance with the presentdisclosure;

FIG. 62 is a logic diagram of another example of an analysis systemanalyzing a section of a system in accordance with the presentdisclosure;

FIG. 63 is a logic diagram of another example of an analysis systemanalyzing a section of a system in accordance with the presentdisclosure;

FIG. 64 is a logic diagram of another example of an analysis systemanalyzing a section of a system in accordance with the presentdisclosure;

FIG. 65 is a logic diagram of another example of an analysis systemanalyzing a section of a system in accordance with the presentdisclosure;

FIG. 66 is a logic diagram of another example of an analysis systemanalyzing a section of a system in accordance with the presentdisclosure;

FIG. 67 is a logic diagram of another example of an analysis systemanalyzing a section of a system in accordance with the presentdisclosure;

FIG. 68 is a logic diagram of an example of an analysis systemgenerating an evaluation output in accordance with the presentdisclosure;

FIG. 69 is a logic diagram of a further example of an analysis systemgenerating an evaluation output in accordance with the presentdisclosure;

FIG. 70 is a logic diagram of a further example of an analysis systemgenerating an evaluation output in accordance with the presentdisclosure;

FIG. 71 is a logic diagram of a further example of an analysis systemgenerating an evaluation output in accordance with the presentdisclosure;

FIG. 72 is a logic diagram of a further example of an analysis systemgenerating an evaluation output in accordance with the presentdisclosure;

FIG. 73 is a logic diagram of a further example of an analysis systemgenerating an evaluation output in accordance with the presentdisclosure;

FIG. 74 is a diagram of an example of an analysis system generating anevaluation output for a selected portion of a system in accordance withthe present disclosure;

FIG. 75 is a schematic block diagram of an embodiment of an analysisunit of an analysis system in accordance with the present disclosure;

FIG. 76 is a diagram of an example of a system aspect, evaluation ratingmetrics, and an evaluation aspect of a system in accordance with thepresent disclosure;

FIG. 77 is a diagram of an example of a collection of data in accordancewith the present disclosure;

FIG. 78 is a diagram of another example of a collection of data inaccordance with the present disclosure;

FIG. 79 is a diagram of another example of a collection of data inaccordance with the present disclosure;

FIG. 80 is a diagram of another example of a collection of data inaccordance with the present disclosure;

FIG. 81 is a diagram of another example of a collection of data inaccordance with the present disclosure;

FIG. 82 is a diagram of another example of a collection of data inaccordance with the present disclosure;

FIG. 83 is a diagram of another example of a collection of data inaccordance with the present disclosure;

FIG. 84 is a diagram of another example of a collection of data inaccordance with the present disclosure;

FIG. 85 is a diagram of another example of a collection of data inaccordance with the present disclosure;

FIG. 86 is a diagram of another example of a collection of data inaccordance with the present disclosure;

FIG. 87 is a diagram of another example of a collection of data inaccordance with the present disclosure;

FIG. 88 is a diagram of another example of a collection of data inaccordance with the present disclosure;

FIG. 89 is a schematic block diagram of another embodiment of ananalysis unit in accordance with the present disclosure;

FIG. 90 is a schematic block diagram of an embodiment of an analyze &score module in accordance with the present disclosure;

FIG. 91 is a schematic block diagram of another embodiment of an analyze& score module in accordance with the present disclosure;

FIG. 92 is a schematic block diagram of an embodiment of a rating modulein accordance with the present disclosure;

FIG. 93 is a diagram of an example an evaluation matrix in accordancewith the present disclosure;

FIG. 94 is a schematic block diagram of an embodiment of a sufficiencymodule in accordance with the present disclosure;

FIG. 95 is a schematic block diagram of an embodiment of a quantity ofuse module in accordance with the present disclosure;

FIG. 96 is a schematic block diagram of an embodiment of aneffectiveness module in accordance with the present disclosure;

FIG. 97 is a diagram of an example of an effectiveness module producinga quantified effectiveness of an evaluation metric in accordance withthe present disclosure;

FIG. 98 is a schematic block diagram of an embodiment of an appropriateuse module in accordance with the present disclosure;

FIG. 99 is a diagram of an example of an appropriate use moduleproducing a quantified appropriate of use of an evaluation metric inaccordance with the present disclosure;

FIG. 100 is a schematic block diagram of an embodiment of a consistencyof use module in accordance with the present disclosure;

FIG. 101 is a diagram of an example of a consistency of use moduleproducing a quantified consistency of use of an evaluation metric inaccordance with the present disclosure;

FIG. 102 is a schematic block diagram of an embodiment of anunderstanding, implementation, operation, or self-analysis module inaccordance with the present disclosure;

FIG. 103 is a logic diagram of an example of a module of FIG. 102generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 104 is a logic diagram of a further example of a module of FIG. 102generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 105 is a diagram of an example of a quantity reference scale inaccordance with the present disclosure;

FIG. 106 is a logic diagram of a further example of a module of FIG. 102generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 107 is a logic diagram of a further example of a module of FIG. 102generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 108 is a diagram of an example of a checklist reference scale inaccordance with the present disclosure;

FIG. 109 is a logic diagram of a further example of a module of FIG. 102generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 110 is a schematic block diagram of an embodiment of anunderstanding, implementation, operation, or self-analysis module inaccordance with the present disclosure;

FIG. 111 is a logic diagram of an example of a module of FIG. 110generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 112 is a logic diagram of a further example of a module of FIG. 110generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 113 is a logic diagram of a further example of a module of FIG. 110generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 114 is a logic diagram of a further example of a module of FIG. 110generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 115 is a logic diagram of a further example of a module of FIG. 110generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 116 is a logic diagram of a further example of a module of FIG. 110generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 117 is a schematic block diagram of an embodiment of anunderstanding, implementation, operation, or self-analysis module inaccordance with the present disclosure;

FIG. 118 is a logic diagram of an example of a module of FIG. 117generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 119 is a logic diagram of an example of a module of FIG. 117generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 120 is a logic diagram of an example of a module of FIG. 117generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 121 is a logic diagram of an example of a module of FIG. 117generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 122 is a logic diagram of an example of a module of FIG. 117generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 123 is a logic diagram of an example of a module of FIG. 117generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 124 is a logic diagram of an example of a module of FIG. 117generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 125 is a schematic block diagram of an embodiment of anunderstanding, implementation, operation, or self-analysis module inaccordance with the present disclosure;

FIG. 126 is a logic diagram of an example of a module of FIG. 125generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 127 is a logic diagram of an example of a module of FIG. 125generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 128 is a logic diagram of an example of a module of FIG. 125generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 129 is a logic diagram of an example of a module of FIG. 125generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 130 is a logic diagram of an example of a module of FIG. 125generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 131 is a logic diagram of an example of a module of FIG. 125generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 132 is a schematic block diagram of an embodiment of anunderstanding, implementation, operation, or self-analysis module inaccordance with the present disclosure;

FIG. 133 is a logic diagram of an example of a module of FIG. 125generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 134 is a logic diagram of an example of a module of FIG. 125generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 135 is a logic diagram of an example of a module of FIG. 125generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 136 is a logic diagram of an example of a module of FIG. 125generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 137 is a logic diagram of an example of a module of FIG. 125generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 138 is a logic diagram of an example of a module of FIG. 125generating an evaluation metric rating in accordance with the presentdisclosure;

FIG. 139 is a logic diagram of an example of an analysis unit generatingan evaluation metric rating with respect to processes in accordance withthe present disclosure;

FIG. 140 is a logic diagram of an example of an analysis unit generatingan evaluation metric rating with respect to policies in accordance withthe present disclosure;

FIG. 141 is a logic diagram of an example of an analysis unit generatingan evaluation metric rating with respect to automation in accordancewith the present disclosure; and

FIG. 142 is a logic diagram of an example of an analysis unit generatingan evaluation metric rating with respect to documentation in accordancewith the present disclosure.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic block diagram of an embodiment of a networkedenvironment that includes one or more networks 14, external data feedssources 15, a plurality of systems 11-13, and an analysis system 10. Theexternal data feed sources 15 includes one or more system proficiencyresources 22, one or more business associated computing devices 23, oneor more non-business associated computing devices 24 (e.g., publiclyavailable servers 27 and subscription based servers 28), one or more BOT(i.e., internet robot) computing devices 25, and one or more bad actorcomputing devices 26. The analysis system 10 includes one or moreanalysis computing entities 16, a plurality of analysis system modules17 (one or more in each of the systems 11-13), and a plurality ofstorage systems 19-21 (e.g., system A private storage 19, system Bprivate storage 20, through system x private storage 21, and otherstorage). Each of the systems 11-13 includes one or more networkinterfaces 18 and many more elements not shown in FIG. 1 .

A computing device may be implemented in a variety of ways. A fewexamples are shown in FIGS. 2A-2D. A computing entity may be implementedin a variety of ways. A few examples are shown in FIGS. 3A-3E.

A storage system 19-21 may be implemented in a variety of ways. Forexample, each storage system is a standalone database. As anotherexample, the storage systems are implemented in a common database. Adatabase is a centralized database, a distributed database, anoperational database, a cloud database, an object-oriented database,and/or a relational database. A storage system 19-21 is coupled to theanalysis system 10 using a secure data pipeline to limit and controlaccess to the storage systems. The secure data pipeline may beimplemented in a variety of ways. For example, the secure data pipelineis implemented on a provide network of the analysis system and/or of asystem under test. As another example, the secure data pipeline isimplemented via the network 14 using access control, using networkcontrols, implementing access and control policies, using encryption,using data loss prevention tools, and/or using auditing tools.

The one or more networks 14 includes one or more wide area networks(WAN), one or more local area networks (LAN), one or more wireless LANs(WLAN), one or more cellular networks, one or more satellite networks,one or more virtual private networks (VPN), one or more campus areanetworks (CAN), one or more metropolitan area networks (MAN), one ormore storage area networks (SAN), one or more enterprise privatenetworks (EPN), and/or one or more other type of networks.

In general, a system proficiency resource 22 is a source for dataregarding best-in-class practices (for system requirements, for systemdesign, for system implementation, and/or for system operation),governmental and/or regulatory requirements, security risk awarenessand/or risk remediation information, security risk avoidance,performance optimization information, system development guidelines,software development guideline, hardware requirements, networkingrequirements, networking guidelines, and/or other system proficiencyguidance. “Framework for Improving Critical Instructure Cybersecurity”,Version 1.1, Apr. 16, 2018 by the National Institute of Standards andTechnology (NIST) is an example of a system proficiency in the form of aguideline for cybersecurity.

A business associated computing device 23 is one that is operated by abusiness associate of the system owner. Typically, the businessassociated computing device 23 has access to at least a limited portionof the system to which the general public does not have access. Forexample, the business associated computing device 23 is operated by avendor of the organization operating the system and is granted limitedaccess for order placement and/or fulfillment. As another example, thebusiness associated computing device 23 is operated by a customer of theorganization operating the system and is granted limited access forplacing orders.

A non-business associated computing device 24 is a computing deviceoperated by a person or entity that does not have a businessrelationship with the organization operating the system. Suchnon-business associated computing device 24 are not granted specialaccess to the system. For example, a non-business associated computingdevice 24 is a publicly available server 27 to which a user computingdevice of the system may access. As another example, a non-businessassociated computing device 24 is a subscription based servers 28 towhich a user computing device of the system may access if it isauthorized by a system administrator of the system to have asubscription and has a valid subscription. As yet another example, thenon-business associated computing device 24 is a computing deviceoperated by a person or business that does not have an affiliation withthe organization operating the system.

A bot (i.e., internet robot) computing device 25 is a computing devicethat runs, with little to no human interaction, to interact with asystem and/or a computing device of a user via the internet or anetwork. There are a variety of types of bots. For example, there aresocial media bots, chatbots, bot crawlers, transaction bots, informationbots, and entertainment bots (e.g., games, art, books, etc.).

A bad actor computing device 26 is a computing device operated by aperson whose use of the computing device is for illegal and/or immoralpurposes. The bad actor computing device 26 may employ a bot to executean illegal and/or immoral purpose. In addition or in the alternative,the person may instruct the bad actor computing device to perform theillegal and/or immoral purpose, such as hacking, planting a worm,planting a virus, stealing data, uploading false data, and so on.

The analysis system 10 is operable to evaluate a system 11-13, orportion thereof, in a variety of ways. For example, the analysis system10 evaluates system A 11, or a portion thereof, by testing theorganization's understanding of its system, or portion thereof; bytesting the organization's implementation of its system, or portionthereof; and/or by testing the system's, or portion thereof; operation.As a specific example, the analysis system 10 tests the organization'sunderstanding of its system requirements for the implementation and/oroperation of its system, or portion thereof. As another specificexample, the analysis system 10 tests the organization's understandingof its software maintenance policies and/or procedures. As anotherspecific example, the analysis system 10 tests the organization'sunderstanding of its cybersecurity policies and/or procedures.

There is an almost endless combination of ways in which the analysissystem 10 can evaluate a system 11-13, which may be a computer system, acomputer network, an enterprise system, and/or other type of system thatincludes computing devices operating software. For example, the analysissystem 10 evaluates a system aspect (e.g., the system or a portion ofit) based on an evaluation aspect (e.g., options for how the system, orportion thereof, can be evaluated) in view of evaluation rating metrics(e.g., how the system, or portion thereof, is evaluated) to produce ananalysis system output (e.g., an evaluation rating, deficiencyidentification, and/or deficiency auto-correction).

The system aspect (e.g., the system or a portion thereof) includes aselection of one or more system elements of the system, a selection ofone or more system criteria, and/or a selection of one or more systemmodes. A system element of the system includes one or more system assetswhich is a physical asset of the system and/or a conceptual asset of thesystem. For example, a physical asset is a computing entity, a computingdevice, a user software application, a system software application(e.g., operating system, etc.), a software tool, a network softwareapplication, a security software application, a system monitoringsoftware application, and the like. As another example, a conceptualasset is a hardware architectural layout, or portion thereof, and/or asoftware architectural layout, or portion thereof.

A system element and/or system asset may be identified in a variety ofways. For example, it is identifiably by its use and/or location withinthe organization. As a specific example, a system element and/or systemasset is identified by an organizational identifier, a division of theorganization identifier, a department of a division identifier, a groupof a department identifier, and/or a sub-group of a group identifier. Inthis manner, if the entire system is to be evaluated, the organizationidentifier is used to select all of the system elements in the system.If a portion of the system is to be test based on business function,then a division, department, group, and/or sub-group identifier is usedto select the desired portion of the system.

In addition or in the alternative, a system element and/or system assetis identifiable based on a serial number, an IP (internet protocol)address, a vendor name, a type of system element and/or system asset(e.g., computing entity, a particular user software application, etc.),registered user of the system element and/or system asset, and/or otheridentifying metric. In this manner, an individual system element and/orsystem asset can be evaluated and/or a type of system element and/orsystem asset can be evaluated (e.g., a particular user softwareapplication).

A system criteria is regarding a level of the system, or portionthereof, being evaluated. For example, the system criteria includesguidelines, system requirements, system design, system build, andresulting system. As a further example, the guidelines (e.g., businessobjectives, security objectives, NIST cybersecurity guidelines, systemobjectives, governmental and/or regulatory requirements, third partyrequirements, etc.) are used to develop the system requirements, whichare used to design the system, which is used to the build the resultingsystem. As such, the system, or potion thereof, can be evaluated from aguideline level, a system requirements level, a design level, a buildlevel, and/or a resulting system level.

A system mode is regarding a different level of the system, or portionthereof, being evaluated. For example, the system mode includes assets,system functions, and security functions. As such, the system can beevaluated from an assets level, a system function level, and/or asecurity function level.

The evaluation aspect (e.g., options for how the system, or portionthereof, can be evaluated) includes a selection of one or moreevaluation perspectives, a selection of one or more evaluationviewpoints, and/or a selection of one or more evaluation categories,which may further include sub-categories, and sub-categories of thesub-categories). An evaluation perspective is understanding of thesystem, or portion thereof; implementation (e.g., design and build) ofthe system, or portion thereof; operational performance of the system,or portion thereof; or self-analysis of the system, or portion thereof.

An evaluation viewpoint is disclosed information from the system,discovered information about the system by the analysis system, ordesired information about the system obtained by the analysis systemfrom system proficiency resources. The evaluation viewpoint complementsthe evaluation perspective to allow for more in-depth and/or detailedevaluations. For example, the analysis system 10 can evaluate how wellthe system is understood by comparing disclosed data with discovereddata. As another example, the analysis system 10 can evaluate how wellthe system is actually implemented in comparison to a desired level ofimplementation.

The evaluation category includes an identify category, a protectcategory, a detect category, a respond category, and a recover category.Each evaluation category includes a plurality of sub-categories and, atleast some of the sub-categories include their own sub-categories (e.g.,a sub-sub category). For example, the identify category includes thesub-categories of asset management, business environment, governance,risk assessment, risk management, access control, awareness & training,and data security. As a further example, asset management includes thesub-categories of hardware inventory, software inventory, data flowmaps, external system cataloged, resource prioritization, and securityroles. The analysis system 10 can evaluate the system, or portionthereof, in light of one more evaluation categories, in light of anevaluation category and one or more sub-categories, or in light of anevaluation category, a sub-category, and one or more sub-sub-categories.

The evaluation rating metrics (e.g., how the system, or portion thereof,is evaluated) include a selection of process, policy, procedure,certification, documentation, and/or automation. This allows theanalysis system to quantify its evaluation. For example, the analysissystem 10 can evaluate the processes a system, or portion thereof, hasto generate an evaluation rating, to identify deficiencies, and/or toauto-correct deficiencies. As another example, the analysis system 10can evaluate how well the system, or portion thereof, uses the processit has to generate an evaluation rating, to identify deficiencies,and/or to auto-correct deficiencies.

In an example, the analysis computing entity 16 (which includes one ormore computing entities) sends a data gathering request to the analysissystem module 17. The data gathering request is specific to theevaluation to be performed by the analysis system 10. For example, ifthe analysis system 10 is evaluating the understanding of the policies,processes, documentation, and automation regarding the assets built forthe engineering department, then the data gathering request would bespecific to policies, processes, documentation, and automation regardingthe assets built for the engineering department.

The analysis system module 17 is loaded on the system 11-13 and obtainedthe requested data from the system. The obtaining of the data can bedone in a variety of ways. For example, the data is disclosed by one ormore system administrators. The disclosed data corresponds to theinformation the system administrator(s) has regarding the system. Inessence, the disclosed data is a reflection of the knowledge the systemadministrator(s) has regarding the system.

As another example, the analysis system module 17 communicates withphysical assets of the system to discover the data. The communicationmay be direct with an asset. For example, the analysis system module 17sends a request to a particular computing device. Alternatively or inaddition, the communication may be through one or more discovery toolsof the system. For example, the analysis system module 17 communicateswith one or more tools of the system to obtain data regarding datasegregation & boundary, infrastructure management, exploit & malwareprotection, encryption, identity & access management, system monitoring,vulnerability management, and/or data protection.

A tool is a network monitoring tool, a network strategy and planningtool, a network managing tool, a Simple Network Management Protocol(SNMP) tool, a telephony monitoring tool, a firewall monitoring tool, abandwidth monitoring tool, an IT asset inventory management tool, anetwork discovery tool, a network asset discovery tool, a softwarediscovery tool, a security discovery tool, an infrastructure discoverytool, Security Information & Event Management (STEM) tool, a datacrawler tool, and/or other type of tool to assist in discovery ofassets, functions, security issues, implementation of the system, and/oroperation of the system. If the system does not have a particular tool,the analysis system module 17 engages one to discover a particular pieceof data.

The analysis system module 17 provides the gathered data to the analysiscomputing entity 16, which stores the gathered data in a private storage19-21 and processes it. The gathered data is processed alone, incombination with stored data (of the system being evaluated and/oranother system's data), in combination with desired data (e.g., systemproficiencies), in combination with analysis modeling (e.g., riskmodeling, data flow modeling, security modeling, etc.), and/or incombination with stored analytic data (e.g., results of otherevaluations). As a result of the processing, the analysis computingentity 16 produces an evaluation rating, to identify deficiencies,and/or to auto-correct deficiencies. The evaluation results are storedin a private storage and/or in another database.

The analysis system 10 is operable to evaluate a system and/or itseco-system at any level of granularity from the entire system to anindividual asset over a wide spectrum of evaluation options. As anexample, the evaluation is to test understanding of the system, to testthe implementation of the system, and/or to test the operation of thesystem. As another example, the evaluation is to test the system'sself-evaluation capabilities with respect to understanding,implementation, and/or operation. As yet another example, the evaluationis to test policies regarding software tools; to test which softwaretools are prescribed by policy; to test which software tools areprohibited by policy; to test the use of the software tools inaccordance with policy, to test maintenance of software tools inaccordance with policy; to test the sufficiency of the policies, to testthe effectiveness of the policies; and/or to test compliancy with thepolicies.

The analysis system 10 takes an outside perspective to analyze thesystem. From within the system, it is often difficult to test the entiresystem, to test different combinations of system elements, to identifyareas of vulnerabilities (assets and human operators), to identify areasof strength (assets and human operators), and to be proactive. Further,such evaluations are additional tasks the system has to perform, whichmeans it consumes resources (human, physicals assets, and financial).Further, since system analysis is not the primary function of a system(supporting the organization is the system's primary purpose), thesystem analysis is not as thoroughly developed, implemented, and/orexecuted as is possible when its implemented in a stand-alone analysissystem, like system 10.

The primary purpose of the analysis system is to analyze other systemsto determine an evaluation rating, to identify deficiencies in thesystem, and, where it can, auto-correct the deficiencies. The evaluationrating can be regarding how well the system, or portion thereof, isunderstood, how well it is implemented, and/or how well it operates. Theevaluation rating can be regarding how effective the system, or portionthereof, is believed (disclosed data) to support a business function;actually (discovered data) supports a business function; and/or should(desired data) support the business function.

The evaluation rating can be regarding how effective the system, orportion thereof, is believed (disclosed data) to mitigate securityrisks; actually (discovered data) supports mitigating security risks;and/or should (desired data) support mitigating security risks. Theevaluation rating can be regarding how effective the system, or portionthereof, is believed (disclosed data) to respond to security risks;actually (discovered data) supports responding to security risks; and/orshould (desired data) support responding security risks.

The evaluation rating can be regarding how effective the system, orportion thereof, is believed (disclosed data) to be used by people; isactually (discovered data) used by people; and/or should (desired data)be used by people. The evaluation rating can be regarding how effectivethe system, or portion thereof, is believed (disclosed data) to identifyassets of the system; actually (discovered data) identifies assets ofthe system; and/or should (desired data) identify assets of the system.

There are a significant number of combinations in which the analysissystem 10 can evaluate a system 11-13. A primary purpose the analysissystem 10 is help the system 11-13 become more self-healing, moreself-updating, more self-protecting, more self-recovering, moreself-evaluating, more self-aware, more secure, more efficient, moreadaptive, and/or more self-responding. By discovering the strengths,weaknesses, vulnerabilities, and other system limitations in a way thatthe system itself cannot do effectively, the analysis system 10significantly improves the usefulness, security, and efficiency ofsystems 11-13.

FIG. 2A is a schematic block diagram of an embodiment of a computingdevice 40 that includes a plurality of computing resources. Thecomputing resource include a core control module 41, one or moreprocessing modules 43, one or more main memories 45, a read only memory(ROM) 44 for a boot up sequence, cache memory 47, a video graphicsprocessing module 42, a display 48 (optional), an Input-Output (I/O)peripheral control module 46, an I/O interface module 49 (which could beomitted), one or more input interface modules 50, one or more outputinterface modules 51, one or more network interface modules 55, and oneor more memory interface modules 54. A processing module 43 is describedin greater detail at the end of the detailed description of theinvention section and, in an alternative embodiment, has a directionconnection to the main memory 45. In an alternate embodiment, the corecontrol module 41 and the I/O and/or peripheral control module 46 areone module, such as a chipset, a quick path interconnect (QPI), and/oran ultra-path interconnect (UPI).

Each of the main memories 45 includes one or more Random Access Memory(RAM) integrated circuits, or chips. For example, a main memory 45includes four DDR4 (4th generation of double data rate) RAM chips, eachrunning at a rate of 2,400 MHz. In general, the main memory 45 storesdata and operational instructions most relevant for the processingmodule 43. For example, the core control module 41 coordinates thetransfer of data and/or operational instructions between the main memory45 and the memory 56-57. The data and/or operational instructionsretrieve from memory 56-57 are the data and/or operational instructionsrequested by the processing module or will most likely be needed by theprocessing module. When the processing module is done with the dataand/or operational instructions in main memory, the core control module41 coordinates sending updated data to the memory 56-57 for storage.

The memory 56-57 includes one or more hard drives, one or more solidstate memory chips, and/or one or more other large capacity storagedevices that, in comparison to cache memory and main memory devices,is/are relatively inexpensive with respect to cost per amount of datastored. The memory 56-57 is coupled to the core control module 41 viathe I/O and/or peripheral control module 46 and via one or more memoryinterface modules 54. In an embodiment, the I/O and/or peripheralcontrol module 46 includes one or more Peripheral Component Interface(PCI) buses to which peripheral components connect to the core controlmodule 41. A memory interface module 54 includes a software driver and ahardware connector for coupling a memory device to the I/O and/orperipheral control module 46. For example, a memory interface 54 is inaccordance with a Serial Advanced Technology Attachment (SATA) port.

The core control module 41 coordinates data communications between theprocessing module(s) 43 and the network(s) 14 via the I/O and/orperipheral control module 46, the network interface module(s) 55, and anetwork card 58 or 59. A network card 58 or 59 includes a wirelesscommunication unit or a wired communication unit. A wirelesscommunication unit includes a wireless local area network (WLAN)communication device, a cellular communication device, a Bluetoothdevice, and/or a ZigBee communication device. A wired communication unitincludes a Gigabit LAN connection, a Firewire connection, and/or aproprietary computer wired connection. A network interface module 55includes a software driver and a hardware connector for coupling thenetwork card to the I/O and/or peripheral control module 46. Forexample, the network interface module 55 is in accordance with one ormore versions of IEEE 802.11, cellular telephone protocols, 10/100/1000Gigabit LAN protocols, etc.

The core control module 41 coordinates data communications between theprocessing module(s) 43 and input device(s) 52 via the input interfacemodule(s) 50, the I/O interface 49, and the I/O and/or peripheralcontrol module 46. An input device 52 includes a keypad, a keyboard,control switches, a touchpad, a microphone, a camera, etc. An inputinterface module 50 includes a software driver and a hardware connectorfor coupling an input device to the I/O and/or peripheral control module46. In an embodiment, an input interface module 50 is in accordance withone or more Universal Serial Bus (USB) protocols.

The core control module 41 coordinates data communications between theprocessing module(s) 43 and output device(s) 53 via the output interfacemodule(s) 51 and the I/O and/or peripheral control module 46. An outputdevice 53 includes a speaker, auxiliary memory, headphones, etc. Anoutput interface module 51 includes a software driver and a hardwareconnector for coupling an output device to the I/O and/or peripheralcontrol module 46. In an embodiment, an output interface module 46 is inaccordance with one or more audio codec protocols.

The processing module 43 communicates directly with a video graphicsprocessing module 42 to display data on the display 48. The display 48includes an LED (light emitting diode) display, an LCD (liquid crystaldisplay), and/or other type of display technology. The display has aresolution, an aspect ratio, and other features that affect the qualityof the display. The video graphics processing module 42 receives datafrom the processing module 43, processes the data to produce rendereddata in accordance with the characteristics of the display, and providesthe rendered data to the display 48.

FIG. 2B is a schematic block diagram of an embodiment of a computingdevice 40 that includes a plurality of computing resources similar tothe computing resources of FIG. 2A with the addition of one or morecloud memory interface modules 60, one or more cloud processinginterface modules 61, cloud memory 62, and one or more cloud processingmodules 63. The cloud memory 62 includes one or more tiers of memory(e.g., ROM, volatile (RAM, main, etc.), non-volatile (hard drive,solid-state, etc.) and/or backup (hard drive, tape, etc.)) that isremoted from the core control module and is accessed via a network (WANand/or LAN). The cloud processing module 63 is similar to processingmodule 43 but is remoted from the core control module and is accessedvia a network.

FIG. 2C is a schematic block diagram of an embodiment of a computingdevice 40 that includes a plurality of computing resources similar tothe computing resources of FIG. 2B with a change in how the cloud memoryinterface module(s) 60 and the cloud processing interface module(s) 61are coupled to the core control module 41. In this embodiment, theinterface modules 60 and 61 are coupled to a cloud peripheral controlmodule 63 that directly couples to the core control module 41.

FIG. 2D is a schematic block diagram of an embodiment of a computingdevice 40 that includes a plurality of computing resources, whichincludes include a core control module 41, a boot up processing module66, boot up RAM 67, a read only memory (ROM) 45, a video graphicsprocessing module 42, a display 48 (optional), an Input-Output (I/O)peripheral control module 46, one or more input interface modules 50,one or more output interface modules 51, one or more cloud memoryinterface modules 60, one or more cloud processing interface modules 61,cloud memory 62, and cloud processing module(s) 63.

In this embodiment, the computing device 40 includes enough processingresources (e.g., module 66, ROM 44, and RAM 67) to boot up. Once bootedup, the cloud memory 62 and the cloud processing module(s) 63 functionas the computing device's memory (e.g., main and hard drive) andprocessing module.

FIG. 3A is schematic block diagram of an embodiment of a computingentity 16 that includes a computing device 40 (e.g., one of theembodiments of FIGS. 2A-2D). A computing device may function as a usercomputing device, a server, a system computing device, a data storagedevice, a data security device, a networking device, a user accessdevice, a cell phone, a tablet, a laptop, a printer, a game console, asatellite control box, a cable box, etc.

FIG. 3B is schematic block diagram of an embodiment of a computingentity 16 that includes two or more computing devices 40 (e.g., two ormore from any combination of the embodiments of FIGS. 2A-2D). Thecomputing devices 40 perform the functions of a computing entity in apeer processing manner (e.g., coordinate together to perform thefunctions), in a master-slave manner (e.g., one computing devicecoordinates and the other support it), and/or in another manner.

FIG. 3C is schematic block diagram of an embodiment of a computingentity 16 that includes a network of computing devices 40 (e.g., two ormore from any combination of the embodiments of FIGS. 2A-2D). Thecomputing devices are coupled together via one or more networkconnections (e.g., WAN, LAN, cellular data, WLAN, etc.) and preform thefunctions of the computing entity.

FIG. 3D is schematic block diagram of an embodiment of a computingentity 16 that includes a primary computing device (e.g., any one of thecomputing devices of FIGS. 2A-2D), an interface device (e.g., a networkconnection), and a network of computing devices 40 (e.g., one or morefrom any combination of the embodiments of FIGS. 2A-2D). The primarycomputing device utilizes the other computing devices as co-processorsto execute one or more the functions of the computing entity, as storagefor data, for other data processing functions, and/or storage purposes.

FIG. 3E is schematic block diagram of an embodiment of a computingentity 16 that includes a primary computing device (e.g., any one of thecomputing devices of FIGS. 2A-2D), an interface device (e.g., a networkconnection) 70, and a network of computing resources 71 (e.g., two ormore resources from any combination of the embodiments of FIGS. 2A-2D).The primary computing device utilizes the computing resources asco-processors to execute one or more the functions of the computingentity, as storage for data, for other data processing functions, and/orstorage purposes.

FIG. 4 is a schematic block diagram of another embodiment of a networkedenvironment that includes a system 11 (or system 12 or system 13), theanalysis system 10, one or more networks, one or more system proficiencyresources 22, one or more business associated computing devices 23, oneor more non-business associated computing devices 24 (e.g., publiclyavailable servers 27 and subscription based servers 28), one or more BOTcomputing devices 25, and one or more bad actor computing devices 26.This diagram is similar to FIG. 1 with the inclusion of detail withinthe system proficiency resource(s) 22, with inclusion of detail withinthe system 11, and with the inclusion of detail within the analysissystem module 17.

In addition to the discussion with respect FIG. 1 , a system proficiencyresource 22 is a computing device that provides information regardingbest-in-class assets, best-in-class practices, known protocols, leadingedge information, and/or established guidelines regarding riskassessment, devices, software, networking, data security, cybersecurity,and/or data communication. A system proficiency resource 22 is acomputing device that may also provide information regarding standards,information regarding compliance requirements, information regardinglegal requirements, and/or information regarding regulatoryrequirements.

The system 11 is shown to include three inter-dependent modes: systemfunctions 82, security functions 83, and system assets 84. Systemfunctions 82 correspond to the functions the system executes to supportthe organization's business requirements. Security functions 83correspond to the functions the system executes to support theorganization's security requirements. The system assets 84 are thehardware and/or software platforms that support system functions 82and/or the security functions 83.

The analysis system module 17 includes one or more data extractionmodules 80 and one or more system user interface modules 81. A dataextraction module 80, which will be described in greater detail withreference to one or more subsequent figures, gathers data from thesystem for analysis by the analysis system 10. A system user interfacemodule 81 provides a user interface between the system 11 and theanalysis system 10 and functions to provide user information to theanalysis system 10 and to receive output data from the analysis system.The system user interface module 81 will be described in greater detailwith reference to one or more subsequent figures.

FIG. 5 is a schematic block diagram of another embodiment of a networkedenvironment that includes a system 11 (or system 12 or system 13), theanalysis system 10, one or more networks, one or more system proficiencyresources 22, one or more business associated computing devices 23, oneor more non-business associated computing devices 24 (e.g., publiclyavailable servers 27 and subscription based servers 28), one or more BOTcomputing devices 25, and one or more bad actor computing devices 26.This diagram is similar to FIG. 4 with the inclusion of additionaldetail within the system 11.

In this embodiment, the system 11 includes a plurality of sets of systemassets to support the system functions 82 and/or the security functions83. For example, a set of system assets supports the system functions 82and/or security functions 83 for a particular business segment (e.g., adepartment within the organization). As another example, a second set ofsystem assets supports the security functions 83 for a differentbusiness segment and a third set of system assets supports the systemfunctions 82 for the different business segment.

FIG. 6 is a schematic block diagram of another embodiment of a networkedenvironment that includes a system 11 (or system 12 or system 13), theanalysis system 10, one or more networks, one or more system proficiencyresources 22, one or more business associated computing devices 23, oneor more non-business associated computing devices 24 (e.g., publiclyavailable servers 27 and subscription based servers 28), one or more BOTcomputing devices 25, and one or more bad actor computing devices 26.This diagram is similar to FIG. 5 with the inclusion of additionaldetail within the system 11.

In this embodiment, the system 11 includes a plurality of sets of systemassets 84, system functions 82, and security functions 83. For example,a set of system assets 84, system functions 82, and security functions83 supports one department in an organization and a second set of systemassets 84, system functions 82, and security functions 83 supportsanother department in the organization.

FIG. 7 is a schematic block diagram of another embodiment of a networkedenvironment that includes a system 11 (or system 12 or system 13), theanalysis system 10, one or more networks, one or more system proficiencyresources 22, one or more business associated computing devices 23, oneor more non-business associated computing devices 24 (e.g., publiclyavailable servers 27 and subscription based servers 28), one or more BOTcomputing devices 25, and one or more bad actor computing devices 26.This diagram is similar to FIG. 4 with the inclusion of additionaldetail within the system 11.

In this embodiment, the system 11 includes system assets 84, systemfunctions 82, security functions 83, and self-evaluation functions 85.The self-evaluation functions 85 are supported by the system assets 84and are used by the system to evaluate its assets, is system functions,and its security functions. In general, self-evaluates looks at system'sability to analyze itself for self-determining it's understanding(self-aware) of the system; self-determining the implementation of thesystem, and/or self-determining operation of the system. In addition,the self-evaluation may further consider the system's ability toself-heal, self-update, self-protect, self-recover, self-evaluate,and/or self-respond. The analysis system 10 can evaluate theunderstanding, implementation, and/or operation of the self-evaluationfunctions.

FIG. 8 is a schematic block diagram of another embodiment of a networkedenvironment having a system 11 (or system 12 or system 13), the analysissystem 10, one or more networks represented by networkinginfrastructure, one or more system proficiency resources 22, one or morebusiness associated computing devices 23, one or more publicly availableservers 27, one or more subscription based servers 28, one or more BOTcomputing devices 25, and one or more bad actor computing devices 26.

In this embodiment, the system 11 is shown to include a plurality ofphysical assets dispersed throughout a geographic region (e.g., abuilding, a town, a county, a state, a country). Each of the physicalassets includes hardware and software to perform its respectivefunctions within the system. A physical asset is a computing entity(CE), a public or provide networking device (ND), a user access device(UAD), or a business associate access device (BAAD).

A computing entity may be a user device, a system admin device, aserver, a printer, a data storage device, etc. A network device may be alocal area network device, a network card, a wide area network device,etc. A user access device is a portal that allows authorizes users ofthe system to remotely access the system. A business associated accessdevice is a portal that allows authorized business associates of thesystem access the system.

Some of the computing entities are grouped via a common connection to anetwork device, which provides the group of computing entities access toother parts of the system and/or the internet. For example, thehighlighted computing entity may access a publicly available server 25via network devices coupled to the network infrastructure. The analysissystem 10 can evaluation whether this is an appropriate access, theunderstanding of this access, the implementation to enable this access,and/or the operation of the system to support this access.

FIG. 9 is a schematic block diagram of an example of a system section ofa system selected for evaluation similar to FIG. 8 . In this example,only a portion of the system is being tested, i.e., system section undertest 91. As such, the analysis system 10 only evaluates assets, systemfunctions, and/or security functions related to assets within the systemsection under test 91.

FIG. 10 is a schematic block diagram of another example of a systemsection of a system selected for evaluation similar to FIG. 9 . In thisexample, a single computing entity (CE) is being tested, i.e., systemsection under test 91. As such, the analysis system 10 only evaluatesassets, system functions, and/or security functions related to theselected computing entity.

FIG. 11 is a schematic block diagram of an embodiment of a networkedenvironment having a system 11 (or system 12 or system 13), the analysissystem 10, one or more networks 14, one or more system proficiencyresources 22, one or more business associated computing devices 23, oneor more publicly available servers 27, one or more subscription basedservers 28, one or more BOT computing devices 25, and one or more badactor computing devices 26.

In this embodiment, the system 11 is shown to include a plurality ofsystem assets (SA). A system asset (SA) may include one or more systemsub assets (S2A) and a system sub asset (S2A) may include one or moresystem sub-sub assets (S3A). While being a part of the analysis system10, at least one data extraction module (DEM) 80 and at least one systemuser interface module (SUIM) 81 are installed on the system 11.

A system element includes one or more system assets. A system asset (SA)may be a physical asset or a conceptual asset as previously described.As an example, a system element includes a system asset of a computingdevice. The computing device, which is the SA, includes userapplications and an operating system; each of which are sub assets ofthe computing device (S2A). In addition, the computing device includes anetwork card, memory devices, etc., which are sub assets of thecomputing device (S2A). Documents created from a word processing userapplication are sub assets of the word processing user application (S3A)and sub-sub assets of the computing device.

As another example, the system asset (SA) includes a plurality ofcomputing devices, printers, servers, etc. of a department of theorganization operating the system 11. In this example, a computingdevice is a sub asset of the system asset and the software and hardwareof the computing devices are sub-sub assets.

The analysis system 10 may evaluate understanding, implementation,and/or operation of one or more system assets, one or more system subassets, and/or one or more system sub-sub assets, as an asset, as itsupports system functions 82, and/or as it supports security functions.The evaluation may be to produce an evaluation rating, to identifydeficiencies, and/or to auto-correct deficiencies.

FIG. 12 is a schematic block diagram of an embodiment of a system 11that includes a plurality of physical assets 100 coupled to an analysissystem 100. The physical assets 100 include an analysis interface device101, one or more networking devices 102, one or more security devices103, one or more system admin devices 104, one or more user devices 105,one or more storage devices 106, and/or one or more servers 107. Eachdevice may be a computing entity that includes hardware (HW) componentsand software (SW) applications (user, device, drivers, and/or system). Adevice may further include a data extraction module (DEM).

The analysis interface device 101 includes a data extraction module(DEM) 80 and the system user interface module 81 to provide connectivityto the analysis system 10. With the connectivity, the analysis system 10is able to evaluate understanding, implementation, and/or operation ofeach device, or portion thereof, as an asset, as it supports systemfunctions 82, and/or as it supports security functions. For example, theanalysis system 10 evaluates the understanding of networking devices 102as an asset. As a more specific example, the analysis system 10evaluates how well the networking devices 102, its hardware, and itssoftware are understood within the system and/or by the systemadministrators. The evaluation includes how well are the networkingdevices 102, its hardware, and its software documented; how well arethey implemented based on system requirements; how well do they operatebased on design and/or system requirements; how well are they maintainedper system policies and/or procedures; how well are their deficienciesidentified; and/or how well are their deficiencies auto-corrected.

FIG. 13 is a schematic block diagram of another embodiment of anetworked environment having a system 11 that includes a plurality ofsystem assets coupled to an analysis system 10. This embodiment issimilar to the embodiment of FIG. 11 with the addition of additionaldata extraction modules (DEM) 80. In this embodiment, each system asset(SA) is affiliated with its own DEM 80. This allows the analysis system10 to extract data more efficiently than via a single DEM. A furtherextension of this embodiment is that each system sub asset (S2A) couldhave its own DEM 80. As yet a further extension, each system sub-subasset (S3A) could have its own DEM 80.

FIG. 14 is a schematic block diagram of another embodiment of a system11 physical assets 100 coupled to an analysis system 100. The physicalassets 100 include one or more networking devices 102, one or moresecurity devices 103, one or more system admin devices 104, one or moreuser devices 105, one or more storage devices 106, and/or one or moreservers 107. Each device may be a computing entity that includeshardware (HW) components and software (SW) applications (user, system,and/or device).

The system admin device 104 includes one or more analysis system modules17, which includes a data extraction module (DEM) 80 and the system userinterface module 81 to provide connectivity to the analysis system 10.With the connectivity, the analysis system 10 is able to evaluateunderstanding, implementation, and/or operation of each device, orportion thereof, as an asset, as it supports system functions 82, and/oras it supports security functions. For example, the analysis system 10evaluates the implementation of networking devices 102 to support systemfunctions. As a more specific example, the analysis system 10 evaluateshow well the networking devices 102, its hardware, and its software areimplemented within the system to support one or more system functions(e.g., managing network traffic, controlling network access per businessguidelines, policies, and/or processes, etc.). The evaluation includeshow well is the implementation of the networking devices 102, itshardware, and its software documented to support the one or more systemfunctions; how well does their implementation support the one or moresystem functions; how well have their implementation to support the oneor more system functions been verified in accordance with policies,processes, etc.; how well are they updated per system policies and/orprocedures; how well are their deficiencies in support of the one ormore system functions identified; and/or how well are their deficienciesin support of the one or more system functions auto-corrected.

FIG. 15 is a schematic block diagram of another embodiment of a system11 that includes a plurality of physical assets 100 coupled to ananalysis system 100. The physical assets 100 include an analysisinterface device 101, one or more networking devices 102, one or moresecurity devices 103, one or more system admin devices 104, one or moreuser devices 105, one or more storage devices 106, and/or one or moreservers 107. Each device may be a computing entity that includeshardware (HW) components and software (SW) applications (user, device,drivers, and/or system). This embodiment is similar to the embodiment ofFIG. 12 with a difference being that the devices 102-107 do not includea data extraction module (DEM) as is shown in FIG. 12 .

FIG. 16 is a schematic block diagram of another embodiment of a system11 that includes networking devices 102, security devices 103, servers107, storage devices 106, and user devices 105. The system 11 is coupledto the network 14, which provides connectivity to the business associatecomputing device 23. The network 14 is shown to include one or more widearea networks (WAN) 162, one or more wireless LAN (WLAN) and/or LANs164, one or more virtual private networks 166.

The networking devices 102 includes one or more modems 120, one or morerouters 121, one or more switches 122, one or more access points 124,and/or one or more local area network cards 124. The analysis system 10can evaluate the network devices 102 collectively as assets, as theysupport system functions, and/or as they support security functions. Theanalysis system 10 may also evaluate each network device individually asan asset, as it supports system functions, and/or as it supportssecurity functions. The analysis system may further evaluate one or morenetwork devices as part of the physical assets of a system aspect (e.g.,the system or a portion thereof being evaluated with respect to one ormore system criteria and one or more system modes).

The security devices 103 includes one or more infrastructure managementtools 125, one or more encryption software programs 126, one or moreidentity and access management tools 127, one or more data protectionsoftware programs 128, one or more system monitoring tools 129, one ormore exploit and malware protection tools 130, one or more vulnerabilitymanagement tools 131, and/or one or more data segmentation and boundarytools 132. Note that a tool is a program that functions to develop,repair, and/or enhance other programs and/or hardware.

The analysis system 10 can evaluate the security devices 103collectively as assets, as they support system functions, and/or as theysupport security functions. The analysis system 10 may also evaluateeach security device individually as an asset, as it supports systemfunctions, and/or as it supports security functions. The analysis systemmay further evaluate one or more security devices as part of thephysical assets of a system aspect (e.g., the system or a portionthereof being evaluated with respect to one or more system criteria andone or more system modes).

The servers 107 include one or more telephony servers 133, one or moreecommerce servers 134, one or more email servers 135, one or more webservers 136, and/or one or more content servers 137. The analysis system10 can evaluate the servers 103 collectively as assets, as they supportsystem functions, and/or as they support security functions. Theanalysis system 10 may also evaluate each server individually as anasset, as it supports system functions, and/or as it supports securityfunctions. The analysis system may further evaluate one or more serversas part of the physical assets of a system aspect (e.g., the system or aportion thereof being evaluated with respect to one or more systemcriteria and one or more system modes).

The storage devices includes one or more cloud storage devices 138, oneor more storage racks 139 (e.g., a plurality of storage devices mountedin a rack), and/or one or more databases 140. The analysis system 10 canevaluate the storage devices 103 collectively as assets, as they supportsystem functions, and/or as they support security functions. Theanalysis system 10 may also evaluate each storage device individually asan asset, as it supports system functions, and/or as it supportssecurity functions. The analysis system may further evaluate one or morestorage devices as part of the physical assets of a system aspect (e.g.,the system or a portion thereof being evaluated with respect to one ormore system criteria and one or more system modes).

The user devices 105 include one or more landline phones 141, one ormore IP cameras 144, one or more cell phones 143, one or more usercomputing devices 145, one or more IP phones 150, one or more videoconferencing equipment 148, one or more scanners 151, and/or one or moreprinters 142. The analysis system 10 can evaluate the use devices 103collectively as assets, as they support system functions, and/or as theysupport security functions. The analysis system 10 may also evaluateeach user device individually as an asset, as it supports systemfunctions, and/or as it supports security functions. The analysis systemmay further evaluate one or more user devices as part of the physicalassets of a system aspect (e.g., the system or a portion thereof beingevaluated with respect to one or more system criteria and one or moresystem modes).

The system admin devices 104 includes one or more system admin computingdevices 146, one or more system computing devices 194 (e.g., datamanagement, access control, privileges, etc.), and/or one or moresecurity management computing devices 147. The analysis system 10 canevaluate the system admin devices 103 collectively as assets, as theysupport system functions, and/or as they support security functions. Theanalysis system 10 may also evaluate each system admin deviceindividually as an asset, as it supports system functions, and/or as itsupports security functions. The analysis system may further evaluateone or more system admin devices as part of the physical assets of asystem aspect (e.g., the system or a portion thereof being evaluatedwith respect to one or more system criteria and one or more systemmodes).

FIG. 17 is a schematic block diagram of an embodiment of a usercomputing device 105 that includes software 160, a user interface 161,processing resources 163, memory 162 and one or more networking device164. The processing resources 163 include one or more processingmodules, cache memory, and a video graphics processing module.

The memory 162 includes non-volatile memory, volatile memory and/or diskmemory. The non-volatile memory stores hardware IDs, user credentials,security data, user IDs, passwords, access rights data, device IDs, oneor more IP addresses and security software. The volatile memory includessystem volatile memory and user volatile memory. The disk memoryincludes system disk memory and user disk memory. User memory (volatileand/or disk) stores user data and user applications. System memory(volatile and/or disk) stores system applications and system data.

The user interface 104 includes one or more I/O (input/output) devicessuch as video displays, keyboards, mice, eye scanners, microphones,speakers, and other devices that interface with one or more users. Theuser interface 161 further includes one or more physical (PHY) interfacewith supporting software such that the user computing device caninterface with peripheral devices.

The software 160 includes one or more I/O software interfaces (e.g.,drivers) that enable the processing module to interface with othercomponents. The software 160 also includes system applications, userapplications, disk memory software interfaces (drivers) and networksoftware interfaces (drivers).

The networking device 164 may be a network card or network interfacethat intercouples the user computing device 105 to devices external tothe computing device 105 and includes one or more PHY interfaces. Forexample, the network card is a WLAN card. As another example, thenetwork card is a cellular data network card. As yet another example,the network card is an ethernet card.

The user computing device may further include a data extraction module80. This would allow the analysis system 10 to obtain data directly fromthe user computing device. Regardless of how the analysis system 10obtains data regarding the user computing device, the analysis system 10can evaluate the user computing device as an asset, as it supports oneor more system functions, and/or as it supports one or more securityfunctions. The analysis system 10 may also evaluate each element of theuser computing device (e.g., each software application, each drive, eachpiece of hardware, etc.) individually as an asset, as it supports one ormore system functions, and/or as it supports one or more securityfunctions.

FIG. 18 is a schematic block diagram of an embodiment of a server 107that includes software 170, processing resources 171, memory 172 and oneor more networking resources 173. The processing resources 171 includeone or more processing modules, cache memory, and a video graphicsprocessing module. The memory 172 includes non-volatile memory, volatilememory, and/or disk memory. The non-volatile memory stores hardware IDs,user credentials, security data, user IDs, passwords, access rightsdata, device IDs, one or more IP addresses and security software. Thevolatile memory includes system volatile memory and shared volatilememory. The disk memory include server disk memory and shared diskmemory.

The software 170 includes one or more I/O software interfaces (e.g.,drivers) that enable the software 170 to interface with othercomponents. The software 170 includes system applications, serverapplications, disk memory software interfaces (drivers), and networksoftware interfaces (drivers). The networking resources 173 may be oneor more network cards that provides a physical interface for the serverto a network.

The server 107 may further include a data extraction module 80. Thiswould allow the analysis system 10 to obtain data directly from theserver. Regardless of how the analysis system 10 obtains data regardingthe server, the analysis system 10 can evaluate the server as an asset,as it supports one or more system functions, and/or as it supports oneor more security functions. The analysis system 10 may also evaluateeach element of the server (e.g., each software application, each drive,each piece of hardware, etc.) individually as an asset, as it supportsone or more system functions, and/or as it supports one or more securityfunctions.

FIG. 19 is a schematic block diagram of another embodiment of anetworked environment having a system 11 (or system 12 or system 13),the analysis system 10, one or more networks 14, one or more systemproficiency resources 22, one or more business associated computingdevices 23, one or more publicly available servers 27, one or moresubscription based servers 28, one or more BOT computing devices 25, andone or more bad actor computing devices 26.

In this embodiment, the system 11 is shown to include a plurality ofsystem functions (SF). A system function (SF) may include one or moresystem sub functions (S2F) and a system sub function (S2F) may includeone or more system sub-sub functions (S3F). While being a part of theanalysis system 10, at least one data extraction module (DEM) 80 and atleast one system user interface module (SUIM) 81 are installed on thesystem 11.

A system function (SF) includes one or more business operations, one ormore compliance requirements, one or more data flow objectives, one ormore data access control objectives, one or more data integrityobjectives, one or more data storage objectives, one or more data useobjectives, and/or one or more data dissemination objectives. Businessoperation system functions are the primary purpose for the system 11.The system 11 is designed and built to support the operations of thebusiness, which vary from business to business.

In general, business operations include operations regarding criticalbusiness functions, support functions for core business, product and/orservice functions, risk management objectives, business ecosystemobjectives, and/or business contingency plans. The business operationsmay be divided into executive management operations, informationtechnology operations, marketing operations, engineering operations,manufacturing operations, sales operations, accounting operations, humanresource operations, legal operations, intellectual property operations,and/or finance operations. Each type of business operation includessub-business operations, which, in turn may include its ownsub-operations.

For example, engineering operations includes a system function ofdesigning new products and/or product features. The design of a newproduct or feature involves sub-functions of creating designspecifications, creating a design based on the design specification, andtesting the design through simulation and/or prototyping. Each of thesesteps includes sub-steps. For example, for the design of a softwareprogram, the design process includes the sub-sub system functions ofcreating a high level design from the design specifications; creating alow level design from the high level design; and the creating code fromthe low level design.

A compliance requirement may be a regulatory compliance requirement, astandard compliance requirement, a statutory compliance requirement,and/or an organization compliance requirement. For example, there are aregulatory compliance requirements when the organization hasgovernmental agencies as clients. An example of a standard compliancerequirement, encryption protocols are often standardized. DataEncryption Standard (DES), Advanced Encryption Standard (AES), RSA(Rivest-Shamir-Adleman) encryption, and public-key infrastructure (PKI)are examples of encryption type standards HIPAA (health InsurancePortability and Accountability Act) is an example of a statutorycompliance requirement. Examples of organization compliance requirementsinclude use of specific vendor hardware, use of specific vendorsoftware, use of encryption, etc.

A data flow objective is regarding where data can flow, at what ratedata can and should flow, the manner in which the data flow, and/or themeans over which the data flows. As an example of a data flow objective,data for remote storage is to flow via a secure data pipeline using aparticular encryption protocol. As another example of a data flowobjective, ingesting of data should have the capacity to handle a datarate of 100 giga-bits per second.

A data access control objective established which type of personneland/or type of assets can access specific types of data. For example,certain members of the corporate department and human resourcesdepartment have access to employee personnel files, while all othermembers of the organization do not.

A data integrity objective establishes a reliability that, when data isretrieved, it is the data that was stored, i.e., it was not lost,damaged, or corrupted. An example of a data integrity protocol is CyclicRedundancy Check (CRC). Another example of a data integrity protocol isa hash function.

A data storage objective establishes the manner in which data is to bestored. For example, a data storage objective is to store data in a RAIDsystem; in particular, a RAID 6 system. As another example, a datastorage objective is regarding archiving of data and the type of storageto use for archived data.

A data use objective establishes the manner in which data can be used.For example, if the data is for sale, then the data use objective wouldestablish what type of data is for sale, at what price, and what is thetarget customer. As another example, a data use objective establishesread only privileges, editing privileges, creation privileges, and/ordeleting privileges.

A data dissemination objective establishes how the data can be shared.For example, a data dissemination objective is regarding confidentialinformation and indicates how the confidential information should bemarked, who in can be shared with internally, and how it can be sharedexternally, if at all.

The analysis system 10 may evaluate understanding, implementation,and/or operation of one or more system functions, one or more system subfunctions, and/or one or more system sub-sub functions. The evaluationmay be to produce an evaluation rating, to identify deficiencies, and/orto auto-correct deficiencies. For example, the analysis system 10evaluates the understanding of the software development policies and/orprocesses. As another example, the analysis system 10 evaluates the useof software development policies and/or processes to implement asoftware program. As yet another example, analysis system 10 evaluatesthe operation of the software program with respect to the businessoperation, the design specifications, and/or the design.

FIG. 20 is a schematic block diagram of another embodiment of a system11 that includes, from a business operations perspective, divisions181-183, departments, and groups. The business structure of the system11, as in most businesses, is governed by a corporate department 180.The corporate department may have its own sub-system with structures andsoftware tailored to the corporate function of the system. Organizedunder the corporate department 180 are divisions, division 1 181,division 2 182, through division k 183. These divisions may be differentbusiness divisions of a multi-national conglomerate, may be differentfunctional divisions of a business, e.g., finance, marketing, sales,legal, engineering, research and development, etc. Under each division1081-183 include a plurality of departments. Under each department are anumber of groups.

The business structure is generic and can be used to represent thestructure of most conventional businesses and/or organizations. Theanalysis system 10 is able to use this generic structure to create andcategorize the business structure of the system 11. The creation andcategorization of the business structure is done in a number of ways.Firstly, the analysis system 10 accesses corporate organizationdocuments for the business and receive feedback from one or more personsin the business and use these documents and data to initially determineat least partially the business structure. Secondly, the analysis system10 determines the network structure of the other system, investigateidentities of components of the network structure, and construct asub-division of the other system. Then, based upon software used withinthe sub-division, data character, and usage character, the analysissystem 10 identifies more specifically the function of the divisions,departments and groups. In doing so, the analysis system 10 usesinformation known of third-party systems to assist in the analysis.

With the abstraction of the business structure, differing portions ofthe business structure may have different levels of abstraction from acomponent/sub-component/sub-sub-component/system/sub-system/sub-sub-systemlevel based upon characters of differing segments of the business. Forexample. a more detailed level of abstraction for elements of thecorporate and security departments of the business may be taken than forother departments of the business.

FIG. 21 is a schematic block diagram of another embodiment of a businessstructure of the system 11. Shown are a corporate department 180, an ITdepartment 181, division 2 182 through division “k” 183, where k is aninteger equal to or greater than 3. The corporate department 180includes a plurality of hardware devices 260, a plurality of softwareapplications 262, a plurality of business policies 264, a plurality ofbusiness procedures 266, local networking 268, a plurality of securitypolicies 270, a plurality of security procedures 272, data protectionresources 272, data access resources 276, data storage devices 278, apersonnel hierarchy 280, and external networking 282. Based upon anassessment of these assets of the corporate department 180, analysissystem 10 may evaluate the understanding, implementation, and/oroperation of the assets, system functions, and/or security functions ofthe corporate department from a number of different perspectives, aswill be described further with reference to one or more the subsequentfigures.

Likewise, the IT department 181 includes a plurality of hardware devices290, a plurality of software applications 292, a plurality of businesspolicies 294, a plurality of business procedures 296, local networking298, a plurality of security policies 300, a plurality of securityprocedures 302, data protection resources 304, data access resources306, data storage devices 308, a personnel hierarchy 310, and externalnetworking 312. Based upon an assessment of these assets of the ITdepartment 181, the analysis system 10 may evaluate the understanding,implementation, and/or operation of the assets, system functions, and/orsecurity functions of the IT department from a number of differentperspectives, as will be described further with reference to one or moreof the subsequent figures.

FIG. 22 is a schematic block diagram of another embodiment of a division182 of a system that includes multiple departments. The departmentsinclude a marketing department 190, an operations department 191, anengineering department 192, a manufacturing department 193, a salesdepartment 194, and an accounting department 195. Each of thedepartments includes a plurality of components relevant to support thecorresponding business functions and/or security functions of thedivision and of the department. In particular, the marketing department190 includes a plurality of devices, software, security policies,security procedures, business policies, business procedures, dataprotection resources, data access resources, data storage resources, apersonnel hierarchy, local network resources, and external networkresources.

Likewise, each of the operations department 191, the engineeringdepartment 192, the manufacturing department 193, the sales department194, and the accounting department 195 includes a plurality of devices,software, security policies, security procedures, business policies,business procedures, data protection resources, data access resources,data storage resources, a personnel hierarchy, local network resources,and external network resources.

Further, within the business structure, a service mesh may beestablished to more effectively protect important portions of thebusiness from other portions of the business. The service mesh may havemore restrictive safety and security mechanisms for one part of thebusiness than another portion of the business, e.g., manufacturingdepartment service mesh is more restrictive than the sales departmentservice mesh.

The analysis system 10 may evaluate the understanding, implementation,and/or operation of the assets, system functions, and/or securityfunctions of the division 182, of each department, of each type ofsystem elements, and/or each system element. For example, the analysissystem 10 evaluates the data access policies and procedures of eachdepartment. As another example, the analysis system 10 evaluates thedata storage policies, procedures, design, implementation, and/oroperation of data storage within the engineering department 192.

FIG. 23 is a schematic block diagram of another embodiment of anetworked environment having a system 11 (or system 12 or system 13),the analysis system 10, one or more networks 14, one or more systemproficiency resources 22, one or more business associated computingdevices 23, one or more publicly available servers 27, one or moresubscription based servers 28, one or more BOT computing devices 25, andone or more bad actor computing devices 26.

In this embodiment, the system 11 is shown to include a plurality ofsecurity functions (SEF). A security function (SEF) may include one ormore system sub security functions (SE2F) and a security sub function(SE2F) may include one or more security sub-sub functions (SE3F). Whilebeing a part of the analysis system 10, at least one data extractionmodule (DEM) 80 and at least one system user interface module (SUIM) 81are installed on the system 11. As used herein, a security functionincludes a security operation, a security requirement, a securitypolicy, and/or a security objective with respect to data, system access,system design, system operation, and/or system modifications (e.g.,updates, expansion, part replacement, maintenance, etc.).

A security function (SF) includes one or more threat detectionfunctions, one or more threat avoidance functions, one or more threatresolution functions, one or more threat recovery functions, one or morethreat assessment functions, one or more threat impact functions, one ormore threat tolerance functions, one or more business securityfunctions, one or more governance security functions, one or more dataat rest protection functions, one or more data in transit protectionfunctions, and/or one or more data loss prevention functions.

A threat detection function includes detecting unauthorized systemaccess; detecting unauthorized data access; detecting unauthorized datachanges; detecting uploading of worms, viruses, and the like; and/ordetecting bad actor attacks. A threat avoidance function includesavoiding unauthorized system access; avoiding unauthorized data access;avoiding unauthorized data changes; avoiding uploading of worms,viruses, and the like; and/or avoiding bad actor attacks.

A threat resolution function includes resolving unauthorized systemaccess; resolving unauthorized data access; resolving unauthorized datachanges; resolving uploading of worms, viruses, and the like; and/orresolving bad actor attacks. A threat recovery function includesrecovering from an unauthorized system access; recovering from anunauthorized data access; recovering from an unauthorized data changes;recovering from an uploading of worms, viruses, and the like; and/orrecovering from a bad actor attack.

A threat assessment function includes accessing the likelihood of and/ormechanisms for unauthorized system access; accessing the likelihood ofand/or mechanisms for unauthorized data access; accessing the likelihoodof and/or mechanisms for unauthorized data changes; accessing thelikelihood of and/or mechanisms for uploading of worms, viruses, and thelike; and/or accessing the likelihood of and/or mechanisms for bad actorattacks.

A threat impact function includes determining an impact on businessoperations from an unauthorized system access; resolving unauthorizeddata access; determining an impact on business operations from anunauthorized data changes; determining an impact on business operationsfrom an uploading of worms, viruses, and the like; and/or determining animpact on business operations from a bad actor attacks.

A threat tolerance function includes determining a level of tolerancefor an unauthorized system access; determining a level of tolerance foran unauthorized data access; determining a level of tolerance for anunauthorized data changes; determining a level of tolerance for anuploading of worms, viruses, and the like; and/or determining a level oftolerance for a bad actor attacks.

A business security function includes data encryption, handling of thirdparty data, releasing data to the public, and so on. A governancesecurity function includes HIPAA compliance; data creation, data use,data storage, and/or data dissemination for specific types of customers(e.g., governmental agency); and/or the like.

A data at rest protection function includes a data access protocol(e.g., user ID, password, etc.) to store data in and/or retrieve datafrom system data storage; data storage requirements, which include typeof storage, location of storage, and storage capacity; and/or other datastorage security functions.

A data in transit protection function includes using a specific datatransportation protocol (e.g., TCP/IP); using an encryption functionprior to data transmission; using an error encoding function for datatransmission; using a specified data communication path for datatransmission; and/or other means to protect data in transit. A data lossprevention function includes a storage encoding technique (e.g., singleparity encoding, double parity encoding, erasure encoding, etc.); astorage backup technique (e.g., one or two backup copies, erasureencoding, etc.); hardware maintenance and replacement policies andprocesses; and/or other means to prevent loss of data.

The analysis system 10 may evaluate understanding, implementation,and/or operation of one or more security functions, one or more securitysub functions, and/or one or more security sub-sub functions. Theevaluation may be to produce an evaluation rating, to identifydeficiencies, and/or to auto-correct deficiencies. For example, theanalysis system 10 evaluates the understanding of the threat detectionpolicies and/or processes. As another example, the analysis system 10evaluates the use of threat detection policies and/or processes toimplement a security assets. As yet another example, analysis system 10evaluates the operation of the security assets with respect to thethreat detection operation, the threat detection design specifications,and/or the threat detection design.

FIG. 24 is a schematic block diagram of an embodiment of an engineeringdepartment 200 of a division 182 that reports to a corporate department180 of a system 11. The engineering department 200 includes engineeringassets, engineering system functions, and engineering securityfunctions. The engineering assets include security HW & SW, user deviceHW & SW, networking HW & SW, system HW & SW, system monitoring HW & SW,and/or other devices that includes HW and/or SW.

In this example, the organization's system functions includes businessoperations, compliance requirements, data flow objectives, data accessobjectives, data integrity objectives, data storage objectives, data useobjectives, and/or data dissemination objectives. These system functionsapply throughout the system including throughout division 2 and for theengineering department 200 of division 2.

The division 182, however, can issues more restrictive, more secure,and/or more detailed system functions. In this example, the division hasissued more restrictive, secure, and/or detailed business operations(business operations +) and more restrictive, secure, and/or detaileddata access functions (data access +). Similarly, the engineeringdepartment 200 may issue more restrictive, more secure, and/or moredetailed system functions than the organization and/or the division. Inthis example, the engineering department has issued more restrictive,secure, and/or detailed business operations (business operations ++)than the division; has issued more restrictive, secure, and/or detaileddata flow functions (data flow ++) than the organization; has issuedmore restrictive, secure, and/or detailed data integrity functions (dataintegrity ++) than the organization; and has issued more restrictive,secure, and/or detailed data storage functions (data storage ++) thanthe organization.

For example, an organization level business operation regarding thedesign of new products and/or of new product features specifieshigh-level design and verify guidelines. The division issued moredetailed design and verify guidelines. The engineering department issuedeven more detailed design and verify guidelines.

The analysis system 10 can evaluate the compliance with the systemfunctions for the various levels. In addition, the analysis system 10can evaluate that the division issued system functions are compliantwith the organization issued system functions and/or are morerestrictive, more secure, and/or more detailed. Similarly, the analysissystem 10 can evaluate that the engineering department issued systemfunctions are compliant with the organization and the division issuedsystem functions and/or are more restrictive, more secure, and/or moredetailed.

As is further shown in this example, the organization security functionsincludes data at rest protection, data loss prevention, data in transitprotection, threat management, security governance, and businesssecurity. The division has issued more restrictive, more secure, and/ormore detailed business security functions (business security +). Theengineering department has issued more restrictive, more secure, and/ormore detailed data at rest protection (data at rest protection ++), dataloss prevention (data loss prevention ++), and data in transitprotection (data in transit ++).

The analysis system 10 can evaluate the compliance with the securityfunctions for the various levels. In addition, the analysis system 10can evaluate that the division issued security functions are compliantwith the organization issued security functions and/or are morerestrictive, more secure, and/or more detailed. Similarly, the analysissystem 10 can evaluate that the engineering department issued securityfunctions are compliant with the organization and the division issuedsecurity functions and/or are more restrictive, more secure, and/or moredetailed.

FIG. 25 is a schematic block diagram of an example of an analysis system10 evaluating a system element under test 91 of a system 11. The systemelement under test 91 corresponds to a system aspect (or system sector),which includes one or more system elements, one or more system criteria,and one or more system modes.

In this example, the system criteria are shown to includes guidelines,system requirements, system design & system build (systemimplementation), and the resulting system. The analysis system 10 mayevaluate the system, or portion thereof, during initial systemrequirement development, initial design of the system, initial build ofthe system, operation of the initial system, revisions to the systemrequirements, revisions to the system design, revisions to the systembuild, and/or operation of the revised system. A revision to a systemincludes adding assets, system functions, and/or security functions;deleting assets, system functions, and/or security functions; and/ormodifying assets, system functions, and/or security functions.

The guidelines include one or more of business objectives, securityobjectives, NIST cybersecurity guidelines, system objectives,governmental and/or regulatory requirements, third party requirements,etc. and are used to help create the system requirements. Systemrequirements outline the hardware requirements for the system, thesoftware requirements for the system, the networking requirements forthe system, the security requirements for the system, the logical dataflow for the system, the hardware architecture for the system, thesoftware architecture for the system, the logical inputs and outputs ofthe system, the system input requirements, the system outputrequirements, the system's storage requirements, the processingrequirements for the system, system controls, system backup, data accessparameters, and/or specification for other system features.

The system requirements are used to help create the system design. Thesystem design includes a high level design (HDL), a low level design(LLD), a detailed level design (DLD), and/or other design levels. Highlevel design is a general design of the system. It includes adescription of system architecture; a database design; an outline ofplatforms, services, and processes the system will require; adescription of relationships between the assets, system functions, andsecurity functions; diagrams regarding data flow; flowcharts; datastructures; and/or other documentation to enable more detailed design ofthe system.

Low level design is a component level design that is based on the HLD.It provides the details and definitions for every system component(e.g., HW and SW). In particular, LLD specifies the features of thesystem components and component specifications. Detailed level designdescribes the interaction of every component of the system.

The system is built based on the design to produce a resulting system(i.e., the implemented assets). The assets of system operate to performthe system functions and/or security functions.

The analysis system 10 can evaluate the understanding, implementation,operation and/or self-analysis of the system 11 at one or more systemcriteria level (e.g., guidelines, system requirements, systemimplementation (e.g., design and/or build), and system) in a variety ofways.

The analysis system 10 evaluates the understanding of the system (orportion thereof) by determining a knowledge level of the system and/ormaturity level of system. For example, an understanding evaluationinterprets what is known about the system and compares it to what shouldbe known about the system.

As a more specific example, the analysis system evaluates theunderstanding of the guidelines. For instance, the analysis system 10evaluates the policies, processes, procedures, automation,certifications, documentation, and/or other evaluation metric (e.g.,evaluation metrics) regarding the thoroughness of the guidelines tofacilitate the understanding of the guidelines. The more incomplete thedata regarding the evaluation metrics, the more likely the guidelinesare incomplete; which indicates a lack of understanding. The fewernumbers of and/or incompleteness of policies, processes, procedures,automation, documentation, certification, and/or other evaluation metricregarding the creation and/or use of the guidelines, the more likely theguidelines are not well understood (e.g., lower level of knowledgeand/or of system maturity) resulting in a low evaluation rating.

As another more specific example of an understanding evaluation, theanalysis system 10 evaluates the understanding of the systemrequirements. For instance, the analysis system 10 evaluates thepolicies, processes, procedures, automation, certifications,documentation, and/or other evaluation metric (e.g., evaluation metrics)regarding the thoroughness of the system requirements to facilitate theunderstanding of the system requirements. The more incomplete the dataregarding the evaluation metrics, the more likely the systemrequirements are incomplete; which indicates a lack of understanding.The fewer numbers of and/or incompleteness of policies, processes,procedures, automation, documentation, certification, and/or otherevaluation metric regarding the creation and/or use of the systemrequirements, the more likely the system requirements are not wellunderstood (e.g., lower level of knowledge and/or of system maturity)resulting in a low evaluation rating.

As another more specific example of an understanding evaluation, theanalysis system 10 evaluates the understanding of the system design. Forinstance, the analysis system 10 evaluates the policies, processes,procedures, automation, certifications, documentation, and/or otherevaluation metric (e.g., evaluation metrics) regarding the thoroughnessof the system design to facilitate the understanding of the systemdesign. The more incomplete the data regarding the evaluation metrics,the more likely the system design is incomplete; which indicates a lackof understanding. The fewer numbers of and/or incompleteness ofpolicies, processes, procedures, automation, documentation,certification, and/or other evaluation metric regarding the creationand/or use of the system design, the more likely the system design isnot well understood (e.g., lower level of knowledge and/or of systemmaturity) resulting in a low evaluation rating.

As another more specific example of an understanding evaluation, theanalysis system 10 evaluates the understanding of the system build. Forinstance, the analysis system 10 evaluates the policies, processes,procedures, automation, certifications, documentation, and/or otherevaluation metric (e.g., evaluation metrics) regarding the thoroughnessof the system build to facilitate the understanding of the system build.The more incomplete the data regarding the evaluation metrics, the morelikely the system build is incomplete; which indicates a lack ofunderstanding. The fewer numbers of and/or incompleteness of policies,processes, procedures, automation, documentation, certification, and/orother evaluation metric regarding the execution of and/or use of thesystem build, the more likely the system build is not well understood(e.g., lower level of knowledge and/or of system maturity) resulting ina low evaluation rating.

As another more specific example of an understanding evaluation, theanalysis system 10 evaluates the understanding of the system functions.For instance, the analysis system 10 evaluates the policies, processes,procedures, automation, certifications, documentation, and/or otherevaluation metric (e.g., evaluation metrics) regarding the thoroughnessof the system build to facilitate the understanding of the system build.The more incomplete the data regarding the evaluation metrics, the morelikely the system build is incomplete; which indicates a lack ofunderstanding. The fewer numbers of and/or incompleteness of policies,processes, procedures, automation, documentation, certification, and/orother evaluation metric regarding the execution of and/or use of thesystem build, the more likely the system build is not well understood(e.g., lower level of knowledge and/or of system maturity) resulting ina low evaluation rating.

As another more specific example of an understanding evaluation, theanalysis system 10 evaluates the understanding of the securityfunctions. For instance, the analysis system 10 evaluates the policies,processes, procedures, automation, certifications, documentation, and/orother evaluation metric (e.g., evaluation metrics) regarding thethoroughness of the system functions to facilitate the understanding ofthe system functions. The more incomplete the data regarding theevaluation metrics, the more likely the system functions are incomplete;which indicates a lack of understanding. The fewer numbers of and/orincompleteness of policies, processes, procedures, automation,documentation, certification, and/or other evaluation metric regardingthe execution of and/or use of the system functions, the more likely thesystem functions are not well understood (e.g., lower level of knowledgeand/or of system maturity) resulting in a low evaluation rating.

As another more specific example of an understanding evaluation, theanalysis system 10 evaluates the understanding of the system assets. Forinstance, the analysis system 10 evaluates the policies, processes,procedures, automation, certifications, documentation, and/or otherevaluation metric (e.g., evaluation metrics) regarding the thoroughnessof the system assets to facilitate the understanding of the systemassets. The more incomplete the data regarding the evaluation metrics,the more likely the system assets are incomplete; which indicates a lackof understanding. The fewer numbers of and/or incompleteness ofpolicies, processes, procedures, automation, documentation,certification, and/or other evaluation metric regarding the selection,identification, and/or use of the system assets, the more likely thesystem assets are not well understood (e.g., lower level of knowledgeand/or of system maturity) resulting in a low evaluation rating.

The analysis system 10 also evaluates the implementation of the system(or portion thereof) by determining how well the system is being, wasdeveloped, and/or is being updated. For example, the analysis system 10determines how well the assets, system functions, and/or securityfunctions are being developed, have been developed, and/or are beingupdated based on the guidelines, the system requirements, the systemdesign, and/or the system build.

As a more specific example of an implementation evaluation, the analysissystem 10 evaluates the implementation of the guidelines. For instance,the analysis system 10 evaluates the policies, processes, procedures,automation, certifications, documentation, and/or other evaluationmetric (e.g., evaluation metrics) regarding the development of theguidelines. The more incomplete the data regarding the evaluationmetrics, the more likely the development of the guidelines isincomplete. The fewer numbers of and/or incompleteness of policies,processes, procedures, automation, documentation, certification, and/orother evaluation metric regarding the development of the guidelines, themore likely the guidelines are not well developed (e.g., lower level ofsystem development maturity) resulting in a low evaluation rating.

As another more specific example of an implementation evaluation, theanalysis system 10 evaluates the implementation of the systemrequirements. For instance, the analysis system 10 evaluates thepolicies, processes, procedures, automation, certifications,documentation, and/or other evaluation metric (e.g., evaluation metrics)regarding the development of the system requirements. The moreincomplete the data regarding the evaluation metrics, the more likelythe development of the system requirements is incomplete. The fewernumbers of and/or incompleteness of policies, processes, procedures,automation, documentation, certification, and/or other evaluation metricregarding the development of the system requirements, the more likelythe system requirements are not well developed (e.g., lower level ofsystem development maturity) resulting in a low evaluation rating.

As another more specific example of an implementation evaluation, theanalysis system 10 evaluates the implementation of the system design.For instance, the analysis system 10 evaluates the policies, processes,procedures, automation, certifications, documentation, and/or otherevaluation metric (e.g., evaluation metrics) regarding the developmentof the system design. The more incomplete the data regarding theevaluation metrics, the more likely the development of the system designis incomplete. The fewer numbers of and/or incompleteness of policies,processes, procedures, automation, documentation, certification, and/orother evaluation metric regarding the development of the system design,the more likely the system design is not well developed (e.g., lowerlevel of system development maturity) resulting in a low evaluationrating.

As another more specific example of an implementation evaluation, theanalysis system 10 evaluates the implementation of the system build. Forinstance, the analysis system 10 evaluates the policies, processes,procedures, automation, certifications, documentation, and/or otherevaluation metric (e.g., evaluation metrics) regarding the developmentof the system build. The more incomplete the data regarding theevaluation metrics, the more likely the development of the system buildis incomplete. The fewer numbers of and/or incompleteness of policies,processes, procedures, automation, documentation, certification, and/orother evaluation metric regarding the development of the system build,the more likely the system build is not well developed (e.g., lowerlevel of system development maturity) resulting in a low evaluationrating.

As another more specific example of an implementation evaluation, theanalysis system 10 evaluates the implementation of the system functions.For instance, the analysis system 10 evaluates the policies, processes,procedures, automation, certifications, documentation, and/or otherevaluation metric (e.g., evaluation metrics) regarding the developmentof the system functions. The more incomplete the data regarding theevaluation metrics, the more likely the development of the systemfunctions is incomplete. The fewer numbers of and/or incompleteness ofpolicies, processes, procedures, automation, documentation,certification, and/or other evaluation metric regarding the developmentof the system functions, the more likely the system functions are notwell developed (e.g., lower level of system development maturity)resulting in a low evaluation mting.

As another more specific example of an implementation evaluation, theanalysis system 10 evaluates the implementation of the securityfunctions. For instance, the analysis system 10 evaluates the policies,processes, procedures, automation, certifications, documentation, and/orother evaluation metric (e.g., evaluation metrics) regarding thedevelopment of the security functions. The more incomplete the dataregarding the evaluation metrics, the more likely the development of thesecurity functions is incomplete. The fewer numbers of and/orincompleteness of policies, processes, procedures, automation,documentation, certification, and/or other evaluation metric regardingthe development of the security functions, the more likely the securityfunctions are not well developed (e.g., lower level of systemdevelopment maturity) resulting in a low evaluation mting.

As another more specific example of an implementation evaluation, theanalysis system 10 evaluates the implementation of the system assets.For instance, the analysis system 10 evaluates the policies, processes,procedures, automation, certifications, documentation, and/or otherevaluation metric (e.g., evaluation metrics) regarding the developmentof the system assets. The more incomplete the data regarding theevaluation metrics, the more likely the development of the system assetsis incomplete. The fewer numbers of and/or incompleteness of policies,processes, procedures, automation, documentation, certification, and/orother evaluation metric regarding the development of the system assets,the more likely the system assets are not well developed (e.g., lowerlevel of system development maturity) resulting in a low evaluationrating.

The analysis system 10 also evaluates the operation of the system (orportion thereof) by determining how well the system fulfills itsobjectives. For example, the analysis system 10 determines how well theassets, system functions, and/or security functions to fulfill theguidelines, the system requirements, the system design, the systembuild, the objectives of the system, and/or other purpose of the system.

As a more specific example of an operation evaluation, the analysissystem 10 evaluates the operation (i.e., fulfillment) of the guidelinesby the system requirements. For instance, the analysis system 10evaluates the policies, processes, procedures, automation,certifications, documentation, and/or other evaluation metric (e.g.,evaluation metrics) regarding the fulfillment of the guidelines by thesystem requirements. The more incomplete the data regarding theevaluation metrics, the more likely the fulfillment of the guidelines bythe system requirements is incomplete. The fewer numbers of and/orincompleteness of policies, processes, procedures, automation,documentation, certification, and/or other evaluation metric regardingthe fulfillment of the guidelines by the system requirements, the morelikely the system requirements does not adequately fulfill theguidelines (e.g., lower level of system development maturity) resultingin a low evaluation rating.

As another more specific example of an operation evaluation, theanalysis system 10 evaluates the operation (i.e., fulfillment) of theguidelines and/or the system requirements by the system design. Forinstance, the analysis system 10 evaluates the policies, processes,procedures, automation, certifications, documentation, and/or otherevaluation metric (e.g., evaluation metrics) regarding the fulfillmentof the guidelines and/or the system requirements by the system design.The more incomplete the data regarding the evaluation metrics, the morelikely the fulfillment of the guidelines and/or the system requirementsby the system design is incomplete. The fewer numbers of and/orincompleteness of policies, processes, procedures, automation,documentation, certification, and/or other evaluation metric regardingthe fulfillment of the guidelines and/or the system requirements by thesystem design, the more likely the system design does not adequatelyfulfill the guidelines and/or the system requirements (e.g., lower levelof system operation maturity) resulting in a low evaluation rating.

As another more specific example of an operation evaluation, theanalysis system 10 evaluates the operation (i.e., fulfillment) of theguidelines, the system requirements, and/or the system design by thesystem build. For instance, the analysis system 10 evaluates thepolicies, processes, procedures, automation, certifications,documentation, and/or other evaluation metric (e.g., evaluation metrics)regarding the fulfillment of the guidelines, the system requirements,and/or the system design by the system build. The more incomplete thedata regarding the evaluation metrics, the more likely the fulfillmentof the guidelines, the system requirements, and/or the system design bythe system build is incomplete. The fewer numbers of and/orincompleteness of policies, processes, procedures, automation,documentation, certification, and/or other evaluation metric regardingthe fulfillment of the guidelines, the system requirements, and/or thesystem design by the system build, the more likely the system build doesnot adequately fulfill the guidelines, the system requirements, and/orthe system design (e.g., lower level of system operation maturity)resulting in a low evaluation rating.

As another more specific example of an operation evaluation, theanalysis system 10 evaluates the operation (i.e., fulfillment) of theguidelines, the system requirements, the system design, the systembuild, and/or objectives by the operation of the system in performingthe system functions. For instance, the analysis system 10 evaluates thepolicies, processes, procedures, automation, certifications,documentation, and/or other evaluation metric (e.g., evaluation metrics)regarding the fulfillment of the guidelines, the system requirements,the system design, the system build, and/or objectives regarding theperformance of the system functions by the system. The more incompletethe data regarding the evaluation metrics, the more likely thefulfillment of the guidelines, the system requirements, the systemdesign, the system, and/or the objectives regarding the system functionsis incomplete. The fewer numbers of and/or incompleteness of policies,processes, procedures, automation, documentation, certification, and/orother evaluation metric regarding the fulfillment of the guidelines, thesystem requirements, the system design, the system build, and/or theobjectives, the more likely the system does not adequately fulfill theguidelines, the system requirements, the system design, the systembuild, and/or the objectives regarding the system functions (e.g., lowerlevel of system operation maturity) resulting in a low evaluationrating.

As another more specific example of an operation evaluation, theanalysis system 10 evaluates the operation (i.e., fulfillment) of theguidelines, the system requirements, the system design, the systembuild, and/or objectives by the operation of the system in performingthe security functions. For instance, the analysis system 10 evaluatesthe policies, processes, procedures, automation, certifications,documentation, and/or other evaluation metric (e.g., evaluation metrics)regarding the fulfillment of the guidelines, the system requirements,the system design, the system build, and/or objectives regarding theperformance of the security functions by the system. The more incompletethe data regarding the evaluation metrics, the more likely thefulfillment of the guidelines, the system requirements, the systemdesign, the system, and/or the objectives regarding the securityfunctions is incomplete. The fewer numbers of and/or incompleteness ofpolicies, processes, procedures, automation, documentation,certification, and/or other evaluation metric regarding the fulfillmentof the guidelines, the system requirements, the system design, thesystem build, and/or the objectives, the more likely the system does notadequately fulfill the guidelines, the system requirements, the systemdesign, the system build, and/or the objectives regarding the securityfunctions (e.g., lower level of system operation maturity) resulting ina low evaluation rating.

As another more specific example of an operation evaluation, theanalysis system 10 evaluates the operation (i.e., fulfillment) of theguidelines, the system requirements, the system design, the systembuild, and/or objectives by the operation of the system functions. Forinstance, the analysis system 10 evaluates the policies, processes,procedures, automation, certifications, documentation, and/or otherevaluation metric (e.g., evaluation metrics) regarding the fulfillmentof the guidelines, the system requirements, the system design, thesystem build, and/or objectives regarding the performance of the systemassets. The more incomplete the data regarding the evaluation metrics,the more likely the fulfillment of the guidelines, the systemrequirements, the system design, the system, and/or the objectivesregarding the system assets is incomplete. The fewer numbers of and/orincompleteness of policies, processes, procedures, automation,documentation, certification, and/or other evaluation metric regardingthe fulfillment of the guidelines, the system requirements, the systemdesign, the system build, and/or the objectives, the more likely thesystem assets do not adequately fulfill the guidelines, the systemrequirements, the system design, the system build, and/or the objectives(e.g., lower level of system operation maturity) resulting in a lowevaluation rating.

The analysis system 10 also evaluates the self-analysis capabilities ofthe system (or portion thereof) by determining how well theself-analysis functions are implemented and how they subsequentlyfulfill the self-analysis objectives. In an example, the self-analysiscapabilities of the system are a self-analysis system that overlies thesystem. Accordingly, the overlaid self-analysis system can be evaluatedby the analysis system 10 in a similar manner as the system under test91. For example, the understanding, implementation, and/or operation ofthe overlaid self-analysis system can be evaluated with respect toself-analysis guidelines, self-analysis requirements, design of theself-analysis system, build of the self-analysis system, and/oroperation of the self-analysis system.

As part of the evaluation process, the analysis system 10 may identifydeficiencies and, when appropriate, auto-correct a deficiency. Forexample, the analysis system 10 identifies deficiencies in theunderstanding, implementation, and/or operation of the guidelines, thesystem requirements, the system design, the system build, the resultingsystem, and/or the system objectives. For example, the analysis system10 obtains addition information from the system via a data gatheringprocess (e.g., producing discovered data) and/or from a systemproficiency resource (e.g., producing desired data). The analysis system10 uses the discovered data and/or desired data to identify thedeficiencies. When possible, the analysis system 10 auto-corrects thedeficiencies. For example, when a software tool that aides in thecreation of guidelines and/or system requirements is missing from thesystem's tool set, the analysis system 10 can automatically obtain acopy of the missing software tool for the system.

FIG. 26 is a schematic block diagram of another example of an analysissystem 10 evaluating a system element under test 91. In this example,the analysis system 10 is evaluating the system element under test 91from three evaluation viewpoints: disclosed data, discovered data, anddesired data. Disclosed data is the known data of the system at theoutset of an analysis, which is typically supplied by a systemadministrator and/or is obtained from data files of the system.Discovered data is the data discovered about the system by the analysissystem 10 during the analysis. Desired data is the data obtained by theanalysis system 10 from system proficiency resources regarding desiredguidelines, system requirements, system design, system build, and/orsystem operation.

The evaluation from the three evaluation viewpoints may be doneserially, in parallel, and/or in a parallel-serial combination toproduce three sets of evaluation ratings. One set for disclosed data,one set for discovered data, and one set for desired data.

A set of evaluation ratings includes one or more of: an evaluationrating regarding the understanding of the guidelines; an evaluationrating regarding the understanding of the system requirements; anevaluation rating regarding the understanding of the system design; anevaluation rating regarding the understanding of the system build; anevaluation rating regarding the understanding of the system operation;an evaluation rating regarding the development of the systemrequirements from the guidelines; an evaluation rating regarding thedesign from the system requirements; an evaluation rating regarding thesystem build from the design; an evaluation rating regarding the systemoperation based on the system design and/or system build; an evaluationrating regarding the guidelines; an evaluation rating regarding thesystem requirements; an evaluation rating regarding the system design;an evaluation rating regarding the system build; and/or an evaluationrating regarding the system operation.

FIG. 27 is a schematic block diagram of another example of an analysissystem 10 evaluating a system element under test 91. In this example,the analysis system 10 is evaluating the system element under test 91from three evaluation viewpoints: disclosed data, discovered data, anddesired data with regard to security functions. The evaluation from thethree evaluation viewpoints for the security functions may be doneserially, in parallel, and/or in a parallel-serial combination toproduce three sets of evaluation ratings with respect to securityfunctions: one for disclosed data, one for discovered data, and one fordesired data.

FIG. 28 is a schematic block diagram of another example of an analysissystem 10 evaluating a system element under test 91. In this example,the analysis system 10 is evaluating the system element under test 91from three evaluation viewpoints and from three evaluation modes. Forexample, disclosed data regarding assets, discovered data regardingassets, desired data regarding assets, disclosed data regarding systemfunctions, discovered data regarding system functions, desired dataregarding system functions, disclosed data regarding security functions,discovered data regarding security functions, and desired data regardingsecurity functions.

The evaluation from the nine evaluation viewpoints & evaluation modecombinations may be done serially, in parallel, and/or in aparallel-serial combination to produce nine sets of evaluation ratingsone for disclosed data regarding assets, one for discovered dataregarding assets, one for desired data regarding assets, one fordisclosed data regarding system functions, one for discovered dataregarding system functions, one for desired data regarding functions,one for disclosed data regarding security functions, one for discovereddata regarding security functions, and one for desired data regardingsecurity functions.

FIG. 29 is a schematic block diagram of an example of the functioning ofan analysis system 10 evaluating a system element under test 91.Functionally, the analysis system 10 includes evaluation criteria 211,evaluation mode 212, analysis perspective 213, analysis viewpoint 214,analysis categories 215, data gathering 216, pre-processing 217, andanalysis metrics 218 to produce one or more ratings 219. The evaluationcriteria 211 includes guidelines, system requirements, system design,system build, and system operation. The evaluation mode 212 includesassets, system functions, and security functions. The evaluationcriteria 211 and the evaluation mode 212 are part of the system aspect,which corresponds to the system, or portion thereof, being evaluated.

The analysis perspective 213 includes understanding, implementation,operation, and self-analysis. The analysis viewpoint includes disclosed,discovered, and desired. The analysis categories 215 include identify,protect, detect, respond, and recover. The analysis perspective 213, theanalysis viewpoint 214, and the analysis categories correspond to howthe system, or portion thereof, will be evaluated. For example, thesystem, or portion thereof, is being evaluated regarding theunderstanding of the system's ability to identify assets, systemfunctions, and/or security functions from discovered data.

The analysis metrics 218 includes process, policy, procedure,automation, certification, and documentation. The analysis metric 218and the pre-processing 217 corresponds to manner of evaluation. Forexample, the policies regarding system's ability to identify assets,system functions, and/or security functions from discovered data of thesystem, or portion thereof, are evaluated to produce an understandingevaluation rating.

In an example of operation, the analysis system 10 determines whatportion of the system is evaluated (i.e., a system aspect). As such, theanalysis system 10 determines one or more system elements (e.g.,including one or more system assets which are physical assets and/orconceptual assets), one or more system criteria (e.g., guidelines,system requirements, system design, system build, and/or systemoperation), and one or more system modes (e.g., assets, systemfunctions, and security functions). The analysis system 10 may determinethe system aspect in a variety of ways. For example, the analysis system10 receives an input identifying the system aspect from an authorizedoperator of the system (e.g., IT personnel, executive personnel, etc.).As another example, the analysis system determines the system aspect ina systematic manner to evaluate various combinations of system aspectsas part of an overall system evaluation. The overall system evaluationmay be done one time, periodically, or continuously. As yet anotherexample, the analysis system determines the system aspect as part of asystematic analysis of a section of the system, which may be done onetime, periodically, or continuously.

The analysis system then determines how the system aspect is to beevaluated by selecting one or more analysis perspectives (understanding,implementation, operation, and self-analysis), one or more analysisviewpoints (disclosed, discovered, and desired), and one or moreanalysis categories (identify, protect, detect, respond, and recover).The analysis system 10 may determine how the system aspect is to beevaluated in a variety of ways. For example, the analysis system 10receives an input identifying how the system aspect is to be evaluatedfrom an authorized operator of the system (e.g., IT personnel, executivepersonnel, etc.). As another example, the analysis system determines howthe system aspect is to be evaluated in a systematic manner to evaluatethe system aspect in various combinations of analysis perspectives,analysis viewpoints, and analysis categories as part of an overallsystem evaluation. The overall system evaluation may be done one time,periodically, or continuously. As yet another example, the analysissystem determines how the system aspect is to be evaluated as part of asystematic analysis of a section of the system, which may be done onetime, periodically, or continuously.

The analysis system 10 also determines one or more analysis metrics(e.g., process, policy, procedure, automation, certification, anddocumentation) regarding the manner for evaluating the system aspect inaccordance with how it's to be evaluated. A policy sets out a strategicdirection and includes high-level rules or contracts regarding issuesand/or matters. For example, all software shall be a most recent versionof the software. A process is a set of actions for generating outputsfrom inputs and includes one or more directives for generating outputsfrom inputs. For example, a process regarding the software policy isthat software updates are to be performed by the IT department and allsoftware shall be updated within one month of the release of the newversion of software.

A procedure is the working instructions to complete an action as may beoutlined by a process. For example, the IT department handling softwareupdates includes a procedure that describes the steps for updating thesoftware, verifying that the updated software works, and recording theupdating and verification in a software update log. Automation is inregard to the level of automation the system includes for handlingactions, issues, and/or matters of policies, processes, and/orprocedures. Documentation is in regard to the level of documentation thesystem has regard guidelines, system requirements, system design, systembuild, system operation, system assets, system functions, securityfunctions, system understanding, system implementation, operation of thesystem, policies, processes, procedures, etc. Certification is in regardto certifications of the system, such as maintenance certification,regulatory certifications, etc.

In an example, the analysis system 10 receives an input identifyingmanner in which to evaluate the system aspect from an authorizedoperator of the system (e.g., IT personnel, executive personnel, etc.).As another example, the analysis system determines the manner in whichto evaluate the system aspect in a systematic manner to evaluate thesystem aspect in various combinations of analysis metrics as part of anoverall system evaluation. The overall system evaluation may be done onetime, periodically, or continuously. As yet another example, theanalysis system determines the manner in which to evaluate the systemaspect as part of a systematic analysis of a section of the system,which may be done one time, periodically, or continuously.

Once the analysis system has determined the system aspect, how it is tobe evaluated, and the manner for evaluation, the data gathering function216 gathers data relevant to the system aspect, how it's to beevaluated, and the manner of evaluation from the system 11, fromresources that store system information 210 (e.g., from the system, froma private storage of the analysis system, etc.), and/or from one or moresystem proficiency resources 22. For example, a current evaluation isregarding an understanding (analysis perspective) of policies (analysismetric) to identify (analysis category) assets (evaluation mode) of anengineering department (system elements) regarding operations(evaluation criteria) that the assets perform based on discovered data(analysis viewpoint). As such, the data gathering function 216 gathersdata regarding policies to identify assets of the engineering departmentand the operations they perform using one or more data discovery tools.

The pre-processing function 217 processes the gathered data bynormalizing the data, parsing the data, tagging the data, and/orde-duplicating the data. The analysis system evaluations the processeddata in accordance with the selected analysis metric to produce one ormore ratings 219. For example, the analysis system would produce arating regarding the understanding of policies to identify assets of anengineering department regarding operations that the assets performbased on discovered data. The rating 219 is on a scale from low to high.In this example, a low rating indicates issues with the understandingand a high rating indicates no issues with the understanding.

FIG. 30 is a schematic block diagram of another example of thefunctioning of an analysis system 10 evaluating a system element undertest 91. The functioning of the analysis system includes a deficiencyperspective function 230, a deficiency evaluation viewpoint function 31,and an auto-correction function 233.

The deficiency perspective function 230 receives one or more ratings 219and may also receive the data used to generate the ratings 219. Fromthese inputs, the deficiency perspective function 230 determines whetherthere is an understanding issue, an implementation issue, and/or anoperation issue. For example, an understanding (analysis perspective)issue relates to a low understanding evaluation rating for a specificevaluation regarding policies (analysis metric) to identify (analysiscategory) assets (evaluation mode) of an engineering department (systemelements) regarding operations (evaluation criteria) that the assetsperform based on discovered data (analysis viewpoint).

As another example, an implementation (analysis perspective) issuerelates to a low implementation evaluation rating for a specificevaluation regarding implementation and/or use of policies (analysismetric) to identify (analysis category) assets (evaluation mode) of anengineering department (system elements) regarding operations(evaluation criteria) that the assets perform based on discovered data(analysis viewpoint). As yet another example, an operation (analysisperspective) issue relates to a low operation evaluation rating for aspecific evaluation regarding consistent, reliable, and/or accuratemechanism(s) to identify (analysis category) assets (evaluation mode) ofan engineering department (system elements) regarding operations(evaluation criteria) that the assets perform based on discovered data(analysis viewpoint) and on policies (analysis metric).

When an understanding, implementation, and/or operation issue isidentified, the deficiency evaluation viewpoint function 231 determineswhether the issue(s) is based on disclosed data, discovered data, and/ordesired data. For example, an understanding issue may be based on adifference between disclosed data and discovered data. As a specificexample, the disclosed data includes a policy outline how to identify(analysis category) assets (evaluation mode) of an engineeringdepartment (system elements) regarding operations (evaluation criteria)that the assets perform, which is listed as version 1.12 and a lastrevision date of Oct. 2, 2020. In this specific example, the discovereddata includes the same policy, but is has been updated to version 1.14and the last revision date as Nov. 13, 2020. As such, the deficiencyevaluation viewpoint function identifies a deficiency 232 in thedisclosed data as being an outdated policy.

As another specific example, the disclosed data includes a policyoutline how to identify (analysis category) assets (evaluation mode) ofan engineering department (system elements) regarding operations(evaluation criteria) that the assets perform. The disclosed data alsoshows an inconsistent use and/or application of the policy resulting oneor more assets not being properly identified. In this instance, thedeficiency evaluation viewpoint function identifies a deficiency 232 inthe disclosed data as being inconsistent use and/or application of thepolicy.

The auto-correct function 233 receives a deficiency 232 and interpretsit to determine a deficiency type, i.e., a nature of the understandingissue, the implementation issue, and/or the operation issues. Continuingwith the outdated policy example, the nature of the understanding issueis that there is a newer version of the policy. Since there is a newerversion available, the auto-correct function 233 can update the policyto the newer version for the system (e.g., an auto-correction). Inaddition to making the auto-correction 235, the analysis system createsan accounting 236 of the auto-correction (e.g., creates a record). Therecord includes an identity of the deficiency, date information, whatauto-correction was done, how it was done, verification that it wasdone, and/or more or less data as may be desired for recordingauto-corrections.

As another specific example, a deficiency 232 is discovered that anasset exists in the engineering department that was not included in thedisclosed data. This deficiency may include one or more relateddeficiencies. For example, a deficiency of design, a deficiency ofbuild, a deficiency is oversight of asset installation, etc. Thedeficiencies of design, build, and/or installation oversight can beauto-corrected; the deficiency of an extra asset cannot. With regard tothe deficiency of the extra asset, the analysis system generates areport regarding the extra asset and the related deficiencies.

FIG. 31 is a diagram of an example of evaluation options of an analysissystem 10 for evaluating a system element under test 91. The evaluationoptions are shown in a three-dimensional tabular form. The rows includeanalysis perspective 213 options (e.g., understanding, implementation,and operation). The columns includes analysis viewpoint 214 option(e.g., disclosed, discovered, and desired). The third dimension includesanalysis output 240 options (e.g., ratings 219, deficiencies indisclosed data, deficiencies in discovered data, deficiencies indisclosed to discovered data, deficiencies in disclosed to desired data,deficiencies in discovered to desired data, and auto-correct.

The analysis system 10 can evaluate the system element under test 91(e.g., system aspect) in one or more combinations of a row selection, acolumn selection, and/or a third dimension selection. For example, theanalysis system performs an evaluation from an understandingperspective, a disclosed data viewpoint, and a ratings output. Asanother example, the analysis system performs an evaluation from anunderstanding perspective, all viewpoints, and a ratings output.

FIG. 32 is a diagram of another example of evaluation options of ananalysis system 10 for evaluating a system element under test 91 (e.g.,system aspect). The evaluation options are shown in the form of a table.The rows are assets (physical and conceptual) and the columns are systemfunctions. The analysis system 10 can evaluate the system element undertest 91 (e.g., system aspect) in one or more combinations of a rowselection and a column selection.

For example, the analysis system 10 can evaluate user HW with respect tobusiness operations. As another example, the analysis system 10 canevaluate physical assets with respect to data flow. As another example,the analysis system 10 can evaluate user SW with respect to all systemfunctions.

FIG. 33 is a diagram of another example of evaluation options of ananalysis system 10 for evaluating a system element under test 91 (e.g.,system aspect). The evaluation options are shown in the form of a table.The rows are security functions and the columns are system functions.The analysis system 10 can evaluate the system element under test 91(e.g., system aspect) in one or more combinations of a row selection anda column selection.

For example, the analysis system 10 can evaluate threat detection withrespect to business operations. As another example, the analysis system10 can evaluate all security functions with respect to data flow. Asanother example, the analysis system 10 can evaluate threat avoidancewith respect to all system functions.

FIG. 34 is a diagram of another example of evaluation options of ananalysis system 10 for evaluating a system element under test 91 (e.g.,system aspect). The evaluation options are shown in the form of a table.The rows are assets (physical and conceptual) and the columns aresecurity functions. The analysis system 10 can evaluate the systemelement under test 91 (e.g., system aspect) in one or more combinationsof a row selection and a column selection.

For example, the analysis system 10 can evaluate user HW with respect tothreat recovery. As another example, the analysis system 10 can evaluatephysical assets with respect to threat resolution. As another example,the analysis system 10 can evaluate user SW with respect to all securityfunctions.

FIG. 35 is a schematic block diagram of an embodiment of an analysissystem 10 that includes one or more computing entities 16, one or moredatabases 275, one or more data extraction modules 80, one or moresystem user interface modules 81, and one or more remediation modules257. The computing entity(ies) 16 is configured to include a data inputmodule 250, a pre-processing module 251, a data analysis module 252, ananalytics modeling module 253, an evaluation processing module 254, adata output module 255, and a control module 256. The database 275,which includes one or more databases, stores the private data for aplurality of systems (e.g., systems A-x) and stores analytical data 270of the analysis system 10.

In an example, the system 11 provides input 271 to the analysis system10 via the system user interface module 80. The system user interfacemodule 80 provides a user interface for an administrator of the system11 and provides a s secure end-point of a secure data pipeline betweenthe system 11 and the analysis system 10. While the system userinterface module 81 is part of the analysis system, it is loaded on andis executed on the system 11.

Via the system user interface module 81, the administrator makesselections as to how the system is to be evaluated and the desiredoutput from the evaluation. For example, the administrator selectsevaluate system, which instructs the analysis system 10 to evaluate thesystem from most every, if not every, combination of system aspect(e.g., system element, system criteria, and system mode), evaluationaspect (e.g., evaluation perspective, evaluation viewpoint, andevaluation category), evaluation metric (e.g., process, policy,procedure, automation, documentation, and certification), and analysisoutput (e.g., an evaluation rating, deficiencies identified, andauto-correction of deficiencies). As another example, the administratorselects one or more system aspects, one or more evaluation aspects, oneor more evaluation metrics, and/or one or more analysis outputs.

The analysis system 10 receives the evaluation selections as part of theinput 271. A control module 256 interprets the input 271 to determinewhat part of the system is to be evaluated (e.g., system aspects), howthe system is to be evaluated (e.g., evaluation aspects), the manner inwhich the system is to be evaluated (e.g., evaluation metrics), and/orthe resulting evaluation output (e.g., an evaluation rating, adeficiency report, and/or auto-correction). From the interpretation ofthe input, the control module 256 generates data gathering parameters263, pre-processing parameters 264, data analysis parameters 265, andevaluation parameters 266.

The control module 256 provides the data gathering parameters 263 to thedata input module 250. The data input module 250 interprets the datagathering parameters 263 to determine data to gather. For example, thedata gathering parameters 263 are specific to the evaluation to beperformed by the analysis system 10. As a more specific example, if theanalysis system 10 is evaluating the understanding of the policies,processes, documentation, and automation regarding the assets built foran engineering department, then the data gathering parameters 263 wouldprescribe gathering data related to policies, processes, documentation,and automation regarding the assets built for the engineeringdepartment.

The data input module 250 may gather (e.g., retrieve, request, etc.)from a variety of sources. For example, the data input module 250gathers data 258 from the data extraction module 80. In this example,the data input module 250 provides instructions to the data extractionmodule 80 regarding the data being requested. The data extraction module80 pulls the requested data from system information 210, which may becentralized data of the system, system administration data, and/or datafrom assets of the system.

As another example, the data input module 250 gathers data from one ormore external data feeds 259. A source of an external data feed includesone or more business associate computing devices 23, one or morepublicly available servers 27, and/or one or more subscriber servers 28.Other sources of external data feeds 259 includes bot computing devices25, and/or bad actor computing devices 26. Typically, the data inputmodule 250 does not seek data inputs from bot computing devices 25and/or bad actor computing devices 26 except under certain circumstancesinvolving specific types of cybersecurity risks.

As another example, the data input module 250 gathers system proficiencydata 260 from one or more system proficiency resources 22. As a specificexample, for a data request that includes desired data, the data inputmodule 250 addresses one or more system proficiencies resources 22 toobtain the desired system proficiency data 260. For example, systemproficiency data 260 includes information regarding best-in-classpractices (for system requirements, for system design, for systemimplementation, and/or for system operation), governmental and/orregulatory requirements, security risk awareness and/or risk remediationinformation, security risk avoidance, performance optimizationinformation, system development guidelines, software developmentguideline, hardware requirements, networking requirements, networkingguidelines, and/or other system proficiency guidance.

As another example, the data input module 250 gathers stored data 261from the database 275. The stored data 261 is previously stored datathat is unique to the system 11, is data from other systems, ispreviously processed data, is previously stored system proficiency data,and/or is previously stored data that assists in the current evaluationof the system.

The data input module 250 provides the gathered data to thepre-processing module 251. Based on the pre-processing parameters 264(e.g., normalize, parse, tag, de-duplication, sort, filter, etc.), thepre-processing module 251 processes the gathered data to producepre-processed data 267. The pre-processed data 267 may be stored in thedatabase 275 and later retrieved as stored data 261.

The analysis modeling module 253 retrieves stored data 261 and/or storedanalytics 262 from the database 275. The analysis modeling module 253operates to increase the artificial intelligence of the analysis system10. For example, the analysis modeling module 253 evaluates stored datafrom one or more systems in a variety of ways to test the evaluationprocesses of the analysis system. As a more specific example, theanalysis modeling module 253 models the evaluation of understanding ofthe policies, processes, documentation, and automation regarding theassets built for an engineering department across multiple systems toidentify commonalities and/or deviations. The analysis modeling module253 interprets the commonalities and/or deviations to adjust parametersof the evaluation of understanding and models how the adjustments affectthe evaluation of understanding. If the adjustments have a positiveeffect, the analysis modeling module 253 stores them as analytics 262and/or analysis modeling 268 in the database 275.

The data analysis module 252 receives the pre-processed data 267, thedata analysis parameters 265 and may further receive optional analysismodeling data 268. The data analysis parameters 265 includes identify ofselected evaluation categories (e.g., identify, protect, detect,respond, and recover), identity of selected evaluation sub-categories,identify of selected evaluation sub-sub categories, identity of selectedanalysis metrics (e.g., process, policy, procedure, automation,certification, and documentation), grading parameters for the selectedanalysis metrics (e.g., a scoring scale for each type of analysismetric), identity of selected analysis perspective (e.g., understanding,implementation, operation, and self-analysis), and/or identity ofselected analysis viewpoint (e.g., disclosed, discovered, and desired).

The data analysis module 252 generates one or more ratings 219 for thepre-processed data 267 based on the data analysis parameters 265. Thedata analysis module 252 may adjust the generation of the one or morerating 219 based on the analysis modeling data 268. For example, thedata analysis module 252 evaluates the understanding of the policies,processes, documentation, and automation regarding the assets built foran engineering department based on the pre-processed data 267 to produceat least one evaluation rating 219.

Continuing with this example, the analysis modeling 268 is regarding theevaluation of understanding of the policies, processes, documentation,and automation regarding the assets built for an engineering departmentof a plurality of different organizations operating on a plurality ofdifferent systems. The modeling indicates that if processes are wellunderstood, the understanding of the policies is less significant in theoverall understanding In this instance, the data analysis module 252 mayadjusts its evaluation rating of the understanding to a more favorablyrating if the pre-processed data 267 correlates with the modeling (e.g.,good understanding of processes).

The data analysis module 252 provides the rating(s) 219 to the dataoutput module 255 and to the evaluation processing module 254. The dataoutput module 255 provides the rating(s) 219 as an output 269 to thesystem user interface module 81. The system user interface module 81provides a graphical rendering of the rating(s) 219.

The evaluation processing module 254 processes the rating(s) 219 basedon the evaluation parameters 266 to identify deficiencies 232 and/or todetermine auto-corrections 235. The evaluation parameters 266 provideguidance on how to evaluate the rating(s) 219 and whether to obtain data(e.g., pre-processed data, stored data, etc.) to assist in theevaluation. The evaluation guidance includes how deficiencies are to beidentified. For example, identify the deficiencies based on thedisclosed data, based on the discovered data, based on a differencesbetween the disclosed and discovered data, based on a differencesbetween the disclosed and desired data, and/or based on a differencesbetween the discovered and desired data. The evaluation guidance furtherincludes whether auto-correction is enabled. The evaluation parameters266 may further includes deficiency parameters, which provide a level oftolerance between the disclosed, discovered, and/or desired data whendetermining deficiencies.

The evaluation processing module 254 provides deficiencies 232 and/orthe auto-corrections 235 to the data output module 255. The data outputmodule 255 provides the deficiencies 232 and/or the auto-corrections 235as an output 269 to the system user interface module 81 and to theremediation module 257. The system user interface module 81 provides agraphical rendering of the deficiencies 232 and/or the auto-corrections235.

The remediation module 257 interprets the deficiencies 232 and theauto-corrections 235 to identify auto-corrections to be performed withinthe system. For example, if a deficiency is a computing device having anoutdated user software application, the remediation module 257coordinates obtaining a current copy of the user software application,uploading it on the computing device, and updating maintenance logs.

FIG. 36 is a schematic block diagram of an embodiment of a portion of ananalysis system 10 coupled to a portion of the system 11. In particular,the data output module 255 of the analysis system 10 is coupled to aplurality of remediation modules 257-1 through 257-n. Each remediationmodule 257 is coupled to one or more system assets 280-1 through 280-n.

A remediation module 257 receives a corresponding portion of the output269. For example, remediation module 257-1 receives output 269-1, whichis regarding an evaluation rating, deficiency, and/or an auto-correctionof system asset 280-1. Remediation module 257-1 may auto-correct adeficiency of the system asset or a system element thereof.Alternatively or in addition, the remediation module 257-1 mayquarantine the system asset or system element thereof if the deficiencycannot be auto-corrected and the deficiency exposes the system toundesired risks, undesired liability, and/or undesired performancedegradation.

FIG. 37 is a schematic block diagram of another embodiment of a portionof an analysis system 10 coupled to a portion of the system 11. Inparticular, the data input module 250 of the analysis system 10 iscoupled to a plurality of data extraction modules 80-1 through 80-n.Each data extraction module 80 is coupled to a system data source 290 ofthe system 11. Each of the system data sources produce systeminformation 210 regarding a corresponding portion of the system. Asystem data source 290-1 through 290-n may be an Azure EventHub, CiscoAdvanced Malware Protection (AMP), Cisco Email Security Appliance (ESA),Cisco Umbrella, NetFlow, and/or Syslog. In addition, a system datasource may be a system asset, a system element, and/or a storage devicestoring system information 210.

An extraction data migration module 293 coordinates the collection ofsystem information 210 as extracted data 291-1 through 291-n. Anextraction data coordination module 292 coordinates the forwarding ofthe extracted data 291 as data 258 to the data input module 250.

FIG. 38 is a schematic block diagram of an embodiment of a dataextraction module 80 of an analysis system 10 coupled to a system 11.The data extraction module 80 includes a tool one or more interfacemodules 311, one or more processing module 312, and one or more networkinterfaces 313. The network interface 313 provides a network connectionsthat allows the data extraction module 80 to be coupled to the one ormore computing entities 16 of the analysis system 10. The tool interface311 allows the data extraction module 80 to interact with tools of thesystem 11 to obtain system information from system data sources 290.

The system 11 includes one or more tools that can be accessed by thedata extraction module 80 to obtain system information from one or moredata sources 290-1 through 290-n. The tools include one or more datasegmentation tools 300, one or more boundary detection tools 301, one ormore data protection tools 302, one or more infrastructure managementtools 303, one or more encryption tools 304, one or more exploitprotection tools 305, one or more malware protection tools 306, one ormore identity management tools 307, one or more access management tools308, one or more system monitoring tools, and/or one or morevulnerability management tools 310.

A system tool may also be an infrastructure management tool, a networkmonitoring tool, a network strategy and planning tool, a networkmanaging tool, a Simple Network Management Protocol (SNMP) tool, atelephony monitoring tool, a firewall monitoring tool, a bandwidthmonitoring tool, an IT asset inventory management tool, a networkdiscovery tool, a network asset discovery tool, a software discoverytool, a security discovery tool, an infrastructure discovery tool,Security Information & Event Management (STEM) tool, a data crawlertool, and/or other type of tool to assist in discovery of assets,functions, security issues, implementation of the system, and/oroperation of the system.

Depending on the data gathering parameters, the tool interface 311engages a system tool to retrieve system information. For example, thetool interface 311 engages the identity management tool to identifyassets in the engineering department. The processing module 312coordinates requests from the analysis system 10 and responses to theanalysis system 10.

FIG. 39 is a schematic block diagram of another embodiment of ananalysis system 10 that includes one or more computing entities 16, oneor more databases 275, one or more data extraction modules 80, and oneor more system user interface modules 81. The computing entity(ies) 16is configured to include a data input module 250, a pre-processingmodule 251, a data analysis module 252, an analytics modeling module253, a data output module 255, and a control module 256. The database275, which includes one or more databases, stores the private data for aplurality of systems (e.g., systems A-x) and stores analytical data 270of the analysis system 10.

This embodiment operates similarly to the embodiment of FIG. 35 with theremoval of the evaluation module 254, which produces deficiencies 232and auto-corrections 235, and the removal of the remediation modules257. As such, this analysis system 10 produces evaluation ratings 219 asthe output 269.

FIG. 40 is a schematic block diagram of another embodiment of ananalysis system 10 that is similar to the embodiment of FIG. 39 . Thisembodiment does not include a pre-processing module 251. As such, thedata collected by the data input module 250 is provided directly to thedata analysis module 252.

FIG. 41 is a schematic block diagram of an embodiment of a data analysismodule 252 of an analysis system 10. The data analysis module 252includes a data module 321 and an analysis & score module 336. The datamodule 321 includes a data parse module 320, one or more data storagemodules 322-334, and a source data matrix 335. A data storage module322-334 may be implemented in a variety of ways. For example, a datastorage module is a buffer. As another example, a data storage module isa section of memory (45, 56, 57, and/or 62 of the FIG. 2 series) of acomputing device (e.g., an allocated, or ad hoc, addressable section ofmemory). As another example, a data storage module is a storage unit(e.g., a computing device used primarily for storage). As yet anotherexample, a data storage module is a section of a database (e.g., anallocated, or ad hoc, addressable section of a database).

The data module 321 operates to provide the analyze & score module 336with source data 337 selected from incoming data based on one or moredata analysis parameters 265. The data analysis parameter(s) 265indicate(s) how the incoming data is to be parsed (if at all) and how itis to be stored within the data storage modules 322-334. A data analysisparameter 265 includes system aspect storage parameters 345, evaluationaspect storage parameters 346, and evaluation metric storage parameters347. A system aspect storage parameter 345 may be null or includesinformation to identify one or more system aspects (e.g., systemelement, system criteria, and system mode), how the data relating tosystem aspects is to be parsed, and how the system aspect parsed data isto be stored.

An evaluation aspect storage parameter 346 may be null or includesinformation to identify one or more evaluation aspects (e.g., evaluationperspective, evaluation viewpoint, and evaluation category), how thedata relating to evaluation aspects is to be parsed, and how theevaluation aspect parsed data is to be stored. An evaluation metricstorage parameter 347 may be null or includes information to identifyone or more evaluation metrics (e.g., process, policy, procedure,certification, documentation, and automation), how the data relating toevaluation metrics is to be parsed, and how the evaluation metric parseddata is to be stored. Note that the data module 321 interprets the dataanalysis parameters 265 collectively such that parsing, and storage areconsistent with the parameters.

The data parsing module 320 parses incoming data in accordance with thesystem aspect storage parameters 345, evaluation aspect storageparameters 346, and evaluation metric storage parameters 347, whichgenerally correspond to what part of the system is being evaluation, howthe system is being evaluated, the manner of evaluation, and/or adesired analysis output. As such, incoming data may be parsed in avariety of ways. The data storage modules 322-334 are assigned to storeparsed data in accordance with the storage parameters 345-347. Forexample, the incoming data, which includes pre-processed data 267, otherexternal feed data 259, data 258 received via a data extraction module,stored data 261, and/or system proficiency data 260, is parsed based onsystem criteria (of the system aspect) and evaluation viewpoint (of theevaluation aspect). As a more specific example, the incoming data isparsed into, and stored, as follows:

-   -   disclosed guideline data that is stored in a disclosed guideline        data storage module 322;    -   discovered guideline data that is stored in a discovered        guideline data storage module 323;    -   desired guideline data that is stored in a desired guideline        data storage module 324;    -   disclosed system requirement (sys. req.) data that is stored in        a disclosed system requirement data storage module 325;    -   discovered system requirement (sys. req.) data that is stored in        a discovered system requirement data storage module 326;    -   desired system requirement (sys. req.) data that is stored in a        desired system requirement data storage module 327;    -   disclosed design and/or build data that is stored in a disclosed        design and/or build data storage module 328;    -   discovered design and/or build data that is stored in a        discovered design and/or build data storage module 329;    -   desired design and/or build data that is stored in a desired        design and/or build data storage module 330;    -   disclosed system operation data that is stored in a disclosed        system operation data storage module 331;    -   discovered system operation data that is stored in a discovered        system operation data storage module 332;    -   desired system operation data that is stored in a desired system        operation data storage module 333; and/or    -   other data that is stored in another data storage module 334.

As another example of parsing, the incoming data is parsed based on acombination of one or more system aspects (e.g., system elements, systemcriteria, and system mode) or sub-system aspects thereof, one or moreevaluation aspects (e.g., evaluation perspective, evaluation viewpoint,and evaluation category) or sub-evaluation aspects thereof, and/or oneor more evaluation rating metrics (e.g., process, policy, procedure,certification, documentation, and automation) or sub-evaluation ratingmetrics thereof. As a specific example, the incoming data is parsedbased on the evaluation rating metrics, creating processed parsed data,policy parsed data, procedure parsed data, certification parsed data,documentation parsed data, and automation parsed data. As anotherspecific example, the incoming data is parsed based on the evaluationcategory of identify and its sub-categories of asset management,business environment, governance, risk assessment, risk management,access control, awareness &, training, and/or data security.

As another example of parsing, the incoming data is not parsed, or isminimally parsed. As a specific example, the data is parsed based ontimestamps: data from one time period (e.g., a day) is parsed from dataof another time period (e.g., a different day).

The source data matrix 335, which may be a configured processing module,retrieves source data 337 from the data storage modules 322-334. Theselection corresponds to the analysis being performed by the analyze &score module 336. For example, if the analyze & score module 336 isevaluating the understanding of the policies, processes, documentation,and automation regarding the assets built for the engineeringdepartment, then the source data 337 would be data specific to policies,processes, documentation, and automation regarding the assets built forthe engineering department.

The analyze & score module 336 generates one or more ratings 219 for thesource data 337 in accordance with the data analysis parameters 265 andanalysis modeling 268. The data analysis parameters 265 includes systemaspect analysis parameters 342, evaluation aspect analysis parameters343, and evaluation metric analysis parameters 344. The analyze & scoremodule 336 is discussed in greater detail with reference to FIG. 42 .

FIG. 42 is a schematic block diagram of an embodiment of an analyze andscore module 336 includes a matrix module 341 and a scoring module 348.The matrix module 341 processes an evaluation mode matrix, an evaluationperspective matrix, an evaluation viewpoint matrix, and an evaluationcategories matrix to produce a scoring input. The scoring module 348includes an evaluation metric matrix to process the scoring input datain accordance with the analysis modeling 268 to produce the rating(s)219.

For example, the matrix module 341 configures the matrixes based on thesystem aspect analysis parameters 342 and the evaluation aspect analysisparameters 343 to process the source data 337 to produce the scoringinput data. As a specific example, the system aspect analysis parameters342 and the evaluation aspect analysis parameters 343 indicate assets asthe evaluation mode, understanding as the evaluation perspective,discovered as the evaluation viewpoint, and the identify as theevaluation category.

Accordingly, the matrix module 341 communicates with the source datamatrix module 335 of the data module 321 to obtain source data 337relevant to assets, understanding, discovered, and identify. The matrixmodule 341 may organize the source data 337 using an organization scheme(e.g., by asset type, by evaluation metric type, by evaluationsub-categories, etc.) or keep the source data 337 as a collection ofdata. The matrix module 341 provides the scoring input data 344 as acollection of data or as organized data to the scoring module 348.

Continuing with the example, the scoring module 248 receives the scoringinput data 348 and evaluates in accordance with the evaluation metricanalysis parameters 344 and the analysis modeling 268 to produce therating(s) 219. As a specific example, the evaluation metric analysisparameters 344 indicate analyzing the scoring input data with respect toprocesses. In this instance, the analysis modeling 268 provides ascoring mechanism for evaluating the scoring input data with respect toprocesses to the scoring module 248. For instance, the analysis modeling268 includes six levels regarding processes and a correspondingnumerical rating: none (e.g., 0), inconsistent (e.g., 10), repeatable(e.g., 20), standardized (e.g., 30), measured (e.g., 40), and optimized(e.g., 50).

In addition, the analysis modeling 268 includes analysis protocols forinterpreting the scoring input data to determine its level andcorresponding rating. For example, if there are no processes regardingidentifying assess of the discovered data, then an understanding levelof processes would be none (e.g., 0), since there are no processes. Asanother example, if there are some processes regarding identifyingassess of the discovered data, but there are gaps in the processes(e.g., identifies some assets, but not all, do not produce consistentresults), then an understanding level of processes would be inconsistent(e.g., 10). To determine if there are gaps in the processes, the scoremodule 248 executes the processes of the discovered data to identifyassets. The scoring module 248 also executes one or more asset discoverytools to identify assets and then compares the two results. If there areinconsistencies in the identified assets, then there are gaps in theprocesses.

As a further example, the processes regarding identifying assess of thediscovered data are repeatable (e.g., produces consistent results, butthere are variations in the processes from process to process, and/orthe processes are not all regulated) but not standardized (e.g.,produces consistent results, but there are no appreciable variations inthe processes from process to process, and/or the processes areregulated). If the processes are repeatable but not standardized, thescoring module establishes an understanding level of the processes asrepeatable (e.g., 20).

If the processes are standardized, the scoring module then determineswhether the processes are measured (e.g., precise, exact, and/orcalculated to the task of identifying assets). If not, the scoringmodule establishes an understanding level of the processes asstandardized (e.g., 30).

If the processes are measured, the scoring module then determineswhether the processes are optimized (e.g., up-to-date and improvementassessed on a regular basis as part of system protocols). If not, thescoring module establishes an understanding level of the processes asmeasured (e.g., 40). If so, the scoring module establishes anunderstanding level of the processes as optimized (e.g., 50).

FIG. 43 is a diagram of an example of system aspect, evaluation aspect,evaluation rating metric, and analysis system output options of ananalysis system 10 for analyzing a system 11, or portion thereof. Thesystem aspect corresponds to what part of the system is to be evaluatedby the analysis system. The evaluation aspect indicates how the systemaspect is to be evaluation. The evaluation rating metric indicates themanner of evaluation of the system aspect in accordance with theevaluation aspect. The analysis system output indicates the type ofoutput to be produced by the analysis system based on the evaluation ofthe system aspect in accordance with the evaluation aspect as per theevaluation rating metric.

The system aspect includes system elements, system criteria, and systemmodes. A system element includes one or more system assets which is aphysical asset and/or a conceptual asset. For example, a physical assetis a computing entity, a computing device, a user software application,a system software application (e.g., operating system, etc.), a softwaretool, a network software application, a security software application, asystem monitoring software application, and the like. As anotherexample, a conception asset is a hardware architecture (e.g.,identification of a system's physical components, their capabilities,and their relationship to each other) and/or sub-architectures thereofand a software architecture (e.g., fundamental structures for thesystem's software, their requirements, and inter-relational operations)and sub-architectures thereof.

A system element and/or system asset is identifiable in a variety ofways. For example, it can be identified by an organization identifier(ID), which would be associated with most, if not all, system elementsof a system. As another example, a system element and/or system assetcan be identified by a division ID, where the division is one of aplurality of divisions in the organization. As another example, a systemelement and/or system asset can be identified by a department ID, wherethe department is one of a plurality of departments in a division. Asyet another example, a system element and/or system asset can beidentified by a department ID, where the department is one of aplurality of departments in a division. As a further example, a systemelement and/or system asset can be identified by a group ID, where thedepartment is one of a plurality of groups in a department. As a stillfurther example, a system element and/or system asset can be identifiedby a sub-group ID, where the department is one of a plurality ofsub-groups in a group. With this type of identifier, a collection ofsystem elements and/or system assets can be selected for evaluation byusing an organization ID, a division ID, a department ID, a group ID, ora sub-group ID.

A system element and/or system asset may also be identified based on auser ID, a serial number, vendor data, an IP address, etc. For example,a computing device has a serial number and vendor data. As such, thecomputing device can be identified for evaluation by its serial numberand/or the vendor data. As another example, a software application has aserial number and vendor data. As such, the software application can beidentified for evaluation by its serial number and/or the vendor data.

In addition, an identifier of one system element and/or system asset maylink to one or more other system elements and/or system assets. Forexample, computing device has a device ID, a user ID, and/or a serialnumber to identify it. The computing device also includes a plurality ofsoftware applications, each with its own serial number. In this example,the software identifiers are linked to the computing device identifiersince the software is loaded on the computing device. This type of anidentifier allows a single system asset to be identified for evaluation.

The system criteria includes information regarding the development,operation, and/or maintenance of the system 11. For example, a systemcriteria is a guideline, a system requirement, a system designcomponent, a system build component, the system, and system operation.Guidelines, system requirements, system design, system build, and systemoperation were discussed with reference to FIG. 25 .

The system mode indicates the assets of the system, the system functionsof the system, and/or the security functions of the system are to beevaluated. Assets, system functions, and security functions have beenpreviously discussed with reference to one or more of FIGS. 7-24 and32-34 .

The evaluation aspect, which indicates how the system aspect is to beevaluated, includes evaluation perspective, evaluation viewpoint, andevaluation category. The evaluation perspective includes understanding(e.g., how well the system is known, should be known, etc.);implementation, which includes design and/or build, (e.g., how well isthe system designed, how well should it be designed); systemperformance, and/or system operation (e.g., how well does the systemperform and/or operate, how well should it perform and/or operate); andself-analysis (e.g., how self-aware is the system, how self-healing isthe system, how self-updating is the system).

The evaluation viewpoint includes disclosed data, discovered data, anddesired data. Disclosed data is the known data of the system at theoutset of an analysis, which is typically supplied by a systemadministrator and/or is obtained from data files of the system.Discovered data is the data discovered about the system by the analysissystem during the analysis. Desired data is the data obtained by theanalysis system from system proficiency resources regarding desiredguidelines, system requirements, system design, system build, and/orsystem operation. Differences in disclosed, discovered, and desired dataare evaluated to support generating an evaluation rating, to identifydeficiencies, and/or to determine and provide auto-corrections.

The evaluation category includes an identify category, a protectcategory, a detect category, a respond category, and a recover category.In general, the identify category is regarding identifying assets,system functions, and/or security functions of the system; the protectcategory is regarding protecting assets, system functions, and/orsecurity functions of the system from issues that may adversely affect;the detect category is regarding detecting issues that may, or have,adversely affect assets, system functions, and/or security functions ofthe system; the respond category is regarding responding to issues thatmay, or have, adversely affect assets, system functions, and/or securityfunctions of the system; and the recover category is regardingrecovering from issues that have adversely affect assets, systemfunctions, and/or security functions of the system. Each categoryincludes one or more sub-categories and each sub-category may includeone or more sub-sub categories as discussed with reference to FIGS.44-49 .

The evaluation rating metric includes process, policy, procedure,certification, documentation, and automation. The evaluation ratingmetric may include more or less topics. The analysis system outputoptions include evaluation rating, deficiency identification, anddeficiency auto-correction.

With such a significant number of options with the system aspect, theevaluation aspect, the evaluation rating metrics, and analysis systemoutput options, the analysis system can analyze a system in thousands,or more, combinations. For example, the analysis system 10 could providean evaluation rating for the entire system with respect to itsvulnerability to cyber-attacks. The analysis system 10 could alsoidentify deficiencies in the system's cybersecurity processes, policies,documentation, implementation, operation, assets, and/or securityfunctions based on the evaluation rating. The analysis system 10 couldfurther auto-correct at least some of the deficiencies in the system'scybersecurity processes, policies, documentation, implementation,operation, assets, and/or security functions.

As another example, the analysis system 10 could evaluates the system'srequirements for proper use of software (e.g., authorized to use, validcopy, current version) by analyzing every computing device in the systemas to the system's software use requirements. From this analysis, theanalysis system generates an evaluation rating. The analysis system 10could also identify deficiencies in the compliance with the system'ssoftware use requirements (e.g., unauthorized use, invalid copy,outdated copy). The analysis system 10 could further auto-correct atleast some of the deficiencies in compliance with the system's softwareuse requirements (e.g., remove invalid copies, update outdated copies).

FIG. 44 is a diagram of another example of system aspects, evaluationaspects, evaluation rating metrics, and analysis system output optionsof an analysis system 11. This diagram is similar to FIG. 43 with theexception that this figure illustrates sub-categories and sub-subcategories. Each evaluation category includes sub-categories, which, inturn, include their own sub-sub categories. The various categories,sub-categories, and sub-sub categories corresponds to the categories,sub-categories, and sub-sub categories identified in the “Framework forImproving Critical Instructure Cybersecurity”, Version 1.1, Apr. 16,2018 by the National Institute of Standards and Technology (NIST).

FIG. 45 is a diagram of an example of an identification evaluationcategory that includes a plurality of sub-categories and eachsub-category includes its own plurality of sub-sub-categories. Theidentify category includes the sub-categories of asset management,business environment, governance, risk management, access control,awareness & training, and data security.

The asset management sub-category includes the sub-sub categories of HWinventoried, SW inventoried, data flow mapped out, external systemscataloged, resources have been prioritized, and security roles have beenestablished. The business environment sub-category includes the sub-subcategories of supply chain roles defined, industry criticalinfrastructure identified, business priorities established, criticalservices identified, and resiliency requirements identified.

The governance sub-category includes the sub-sub categories of securitypolicies are established, security factors aligned, and legalrequirements are identified. The risk assessment sub-category includesthe sub-sub categories of vulnerabilities identified, external sourcesare leveraged, threats are identified, business impacts are identified,risk levels are identified, and risk responses are identified. The riskmanagement sub-category includes the sub-sub categories of riskmanagement processes are established, risk tolerances are established,and risk tolerances are tied to business environment.

The access control sub-category includes the sub-sub categories ofremote access control is defined, permissions are defined, and networkintegrity is defined. The awareness & training sub-category includes thesub-sub categories of users are trained, user privileges are known,third party responsibilities are known, executive responsibilities areknown, and IT and security responsibilities are known. The data securitysub-category includes the sub-sub categories of data at rest protocolsare established, data in transit protocols are established, formal assetmanagement protocols are established, adequate capacity of the system isestablished, data leak prevention protocols are established, integritychecking protocols are established, and use and development separationprotocols are established.

FIG. 46 is a diagram of an example of a protect evaluation category thatincludes a plurality of sub-categories and each sub-category includesits own plurality of sub-sub-categories. The protect category includesthe sub-categories of information protection processes and procedures,maintenance, and protective technology.

The information protection processes and procedures sub-categoryincludes the sub-sub categories of baseline configuration ofIT/industrial controls are established, system life cycle management isestablished, configuration control processes are established, backups ofinformation are implemented, policy & regulations for physical operationenvironment are established, improving protection processes areestablished, communication regarding effective protection technologiesis embraced, response and recovery plans are established, cybersecurityin is including in human resources, and vulnerability management plansare established.

The maintenance sub-category includes the sub-sub categories of systemmaintenance & repair of organizational assets programs are establishedand remote maintenance of organizational assets is established. Theprotective technology sub-category includes the sub-sub-categories ofaudit and recording policies are practiced, removable media is protected& use policies are established, access to systems and assets iscontrolled, and communications and control networks are protected.

FIG. 47 is a diagram of an example of a detect evaluation category thatincludes a plurality of sub-categories and each sub-category includesits own plurality of sub-sub-categories. The detect category includesthe sub-categories of anomalies and events, security continuousmonitoring, and detection processes.

The anomalies and events sub-category includes the sub-sub categories ofbaseline of network operations and expected data flows are monitored,detected events are analyzed, event data are aggregated and correlated,impact of events is determined, and incident alert thresholds areestablished. The security continuous monitoring sub-category includesthe sub-sub categories of network is monitored to detect potentialcybersecurity attacks, physical environment is monitored forcybersecurity events, personnel activity is monitored for cybersecurityevents, malicious code is detected, unauthorized mobile codes isdetected, external service provider activity is monitored forcybersecurity events, monitoring for unauthorized personnel,connections, devices, and software is performed, and vulnerability scansare performed. The detection processes sub-category includes the sub-subcategories of roles and responsibilities for detection are defined,detection activities comply with applicable requirements, detectionprocesses are tested, event detection information is communicated, anddetection processes are routinely improved.

FIG. 48 is a diagram of an example of a respond evaluation category thatincludes a plurality of sub-categories and each sub-category includesits own plurality of sub-sub-categories. The respond category includesthe sub-categories of response planning, communications, analysis,mitigation, and improvements.

The response planning sub-category includes the sub-sub category ofresponse plan is executed during and/or after an event. Thecommunications sub-category includes the sub-sub category of personnelroles and order of operation are established, events are reportedconsistent with established criteria, information is shared consistentlyper the response plan, coordination with stakeholders is consistent withthe response plan, and voluntary information is shared with externalstakeholders.

The analysis sub-category includes the sub-sub categories ofnotifications form detection systems are investigated, impact of theincident is understood, forensics are performed, and incidents arecategorized per response plan. The mitigation sub-category includes thesub-sub categories of incidents are contained, incidents are mitigated,and newly identified vulnerabilities are processed. The improvementssub-categories includes the sub-sub categories of response plansincorporate lessons learned, and response strategies are updated.

FIG. 49 is a diagram of an example of a recover evaluation category thatincludes a plurality of sub-categories and each sub-category includesits own plurality of sub-sub-categories. The recover category includesthe sub-categories of recovery plan, improvements, and communication.The recovery plan sub-category includes the sub-sub category of recoveryplan is executed during and/or after an event.

The improvement sub-category includes the sub-sub categories of recoveryplans incorporate lessons learned and recovery strategies are updated.The communications sub-category includes the sub-sub categories ofpublic relations are managed, reputations after an event is repaired,and recovery activities are communicated.

FIG. 50 is a diagram of an example of system aspects, evaluationaspects, evaluation rating metrics, and analysis system output optionsof an analysis system 11 for analyzing a system 11, or portion thereof.For instance, analysis system 11 is evaluating the understanding of theguidelines for identifying assets, protecting the assets from issues,detecting issues that may affect or are affecting the assets, respondingto issues that may affect or are affecting the assets, and recoveringfrom issues that affected the assets of a department based on discloseddata.

For this specific example, the analysis system 10 obtains disclosed datafrom the system regarding the guidelines associated with the assets ofthe department. From the disclosed data, the analysis system renders anevaluation rating for the understanding of the guidelines foridentifying assets. The analysis system renders a second evaluationrating for the understanding of the guidelines regarding protection ofthe assets from issues. The analysis system renders a third evaluationrating for the understanding of the guidelines regarding detection ofissues that may affect or are affecting the assets.

The analysis system renders a fourth evaluation rating for theunderstanding of the guidelines regarding responds to issues that mayaffect or are affecting the assets. The analysis system renders a fifthevaluation rating for the understanding of the guidelines regardingrecovery from issues that affected the assets of a department based ondisclosed data. The analysis system may render an overall evaluationrating for the understanding of the guidelines based on the firstthrough fifth evaluation ratings.

As another example, the analysis system 11 evaluates the understandingof guidelines used to determine what assets should be included in thedepartment, how the assets should be protected from issues, how issuesthat may affect or are affecting the assets are detect, how to respondto issues that may affect or are affecting the assets, and how theassets will recover from issues that may affect or are affecting thembased on disclosed data. In this example, the analysis system renders anevaluation rating for the understanding of the guidelines regarding whatassets should be in the department. The analysis system renders a secondevaluation rating for the understanding of the guidelines regarding howthe assets should be protected from issues. The analysis system rendersa third evaluation rating for the understanding of the guidelinesregarding how to detect issues that may affect or are affecting theassets.

The analysis system renders a fourth evaluation rating for theunderstanding of the guidelines regarding how to respond to issues thatmay affect or are affecting the assets. The analysis system renders afifth evaluation rating for the understanding of the guidelinesregarding how to recover from issues that affected the assets of adepartment based on disclosed data. The analysis system may render anoverall evaluation rating for the understanding based on the firstthrough fifth evaluation ratings.

FIG. 51 is a diagram of an example of system aspects, evaluationaspects, evaluation rating metrics, and analysis system output optionsof an analysis system 11 for analyzing a system 11, or portion thereof.For instance, analysis system 11 is evaluating the understanding of thesystem design for identifying assets, protecting the assets from issues,detecting issues that may affect or are affecting the assets, respondingto issues that may affect or are affecting the assets, and recoveringfrom issues that affected the assets of a department based on discloseddata.

For this specific example, the analysis system 10 obtains disclosed datafrom the system regarding the system design associated with the assetsof the department. From the disclosed data, the analysis system rendersan evaluation rating for the understanding of the system design foridentifying assets. The analysis system renders a second evaluationrating for the understanding of the system design regarding protectionof the assets from issues. The analysis system renders a thirdevaluation rating for the understanding of the system design regardingdetection of issues that may affect or are affecting the assets.

The analysis system renders a fourth evaluation rating for theunderstanding of the system design regarding responds to issues that mayaffect or are affecting the assets. The analysis system renders a fifthevaluation rating for the understanding of the system design regardingrecovery from issues that affected the assets of a department based ondisclosed data. The analysis system may render an overall evaluationrating for the understanding based on the first through fifth evaluationratings.

As another example, the analysis system 11 evaluates the understandingof system design used to determine what assets should be included in thedepartment, how the assets should be protected from issues, how issuesthat may affect or are affecting the assets are detect, how to respondto issues that may affect or are affecting the assets, and how theassets will recover from issues that may affect or are affecting thembased on disclosed data. In this example, the analysis system renders anevaluation rating for the understanding of the system design regardingwhat assets should be in the department. The analysis system renders asecond evaluation rating for the understanding of the system designregarding how the assets should be protected from issues. The analysissystem renders a third evaluation rating for the understanding of thesystem design regarding how to detect issues that may affect or areaffecting the assets.

The analysis system renders a fourth evaluation rating for theunderstanding of the system design regarding how to respond to issuesthat may affect or are affecting the assets. The analysis system rendersa fifth evaluation rating for the understanding of the system designregarding how to recover from issues that affected the assets of adepartment based on disclosed data. The analysis system may render anoverall evaluation rating for the understanding based on the firstthrough fifth evaluation ratings.

FIG. 52 is a diagram of an example of system aspects, evaluationaspects, evaluation rating metrics, and analysis system output optionsof an analysis system 11 for analyzing a system 11, or portion thereof.For instance, analysis system 11 is evaluating the understanding of theguidelines, system requirements, and system design for identifyingassets, protecting the assets from issues, detecting issues that mayaffect or are affecting the assets, responding to issues that may affector are affecting the assets, and recovering from issues that affectedthe assets of a department based on disclosed data and discovered data.

For this specific example, the analysis system 10 obtains disclosed dataand discovered from the system regarding guidelines, systemrequirements, and system design associated with the assets of thedepartment. From the disclosed data and discovered data, the analysissystem renders one or more first evaluation ratings (e.g., one for eachof guidelines, system requirements, and system design, or one for allthree) for the understanding of the guidelines, system requirements, andsystem design for identifying assets. The analysis system renders one ormore second evaluation ratings for the understanding of the guidelines,system requirements, and system design regarding protection of theassets from issues. The analysis system renders one or more thirdevaluation ratings for the understanding of the guidelines, systemrequirements, and system design regarding detection of issues that mayaffect or are affecting the assets.

The analysis system renders one or more fourth evaluation ratings forthe understanding of the guidelines, system requirements, and systemdesign regarding responds to issues that may affect or are affecting theassets. The analysis system renders one or more fifth evaluation ratingsfor the understanding of the guidelines, system requirements, and systemdesign regarding recovery from issues that affected the assets of adepartment based on disclosed data. The analysis system may render anoverall evaluation rating for the understanding based on the one or morefirst through one or more fifth evaluation ratings.

The analysis system 11 may further render an understanding evaluationrating regarding how well the discovered data correlates with thedisclosed data. In other words, evaluate the knowledge level of thesystem. In this example, the analysis system compares the disclosed datawith the discovered data. If they substantially match, the understandingof the system would receive a relatively high evaluation rating. Themore the disclosed data differs from the discovered data, the lower theunderstanding evaluation rating will be.

As another example, the analysis system 11 evaluates the understandingof guidelines, system requirements, and system design used to determinewhat assets should be included in the department, how the assets shouldbe protected from issues, how issues that may affect or are affectingthe assets are detect, how to respond to issues that may affect or areaffecting the assets, and how the assets will recover from issues thatmay affect or are affecting them based on disclosed data and discovereddata. In this example, the analysis system renders one or more firstevaluation ratings for the understanding of the guidelines, systemrequirements, and system design regarding what assets should be in thedepartment. The analysis system renders one or more second evaluationratings for the understanding of the guidelines, system requirements,and system design regarding how the assets should be protected fromissues. The analysis system renders one or more third evaluation ratingsfor the understanding of the guidelines, system requirements, and systemdesign regarding how to detect issues that may affect or are affectingthe assets.

The analysis system renders one or more fourth evaluation ratings forthe understanding of the guidelines, system requirements, and systemdesign regarding how to respond to issues that may affect or areaffecting the assets. The analysis system renders one or more fifthevaluation ratings for the understanding of the guidelines, systemrequirements, and system design regarding how to recover from issuesthat affected the assets of a department based on disclosed data. Theanalysis system may render an overall evaluation rating for theunderstanding of the guidelines, system requirements, and system designbased on the one or more first through the one or more fifth evaluationratings.

FIG. 53 is a diagram of an example of system aspects, evaluationaspects, evaluation rating metrics, and analysis system output optionsof an analysis system 11 for analyzing a system 11, or portion thereof.For instance, analysis system 11 is evaluating the implementation forand operation of identifying assets of a department, protecting theassets from issues, detecting issues that may affect or are affectingthe assets, responding to issues that may affect or are affecting theassets, and recovering from issues that affected the assets per theguidelines, system requirements, system design, system build, andresulting system based on disclosed data and discovered data.

For this specific example, the analysis system 10 obtains disclosed dataand discovered data from the system regarding the guidelines, systemrequirements, system design, system build, and resulting systemassociated with the assets of the department. From the disclosed dataand discovered data, the analysis system renders one or more firstevaluation ratings (e.g., one for each of guidelines, systemrequirements, system design, system build, resulting system with respectto each of implementation and operation or one for all of them) for theimplementation and operation of identifying the assets per theguidelines, system requirements, system design, system build, andresulting system. The analysis system renders one or more secondevaluation ratings for the implementation and operation of protectingthe assets from issues per the guidelines, system requirements, systemdesign, system build, and resulting system.

The analysis system renders one or more third evaluation ratings for theimplementation and operation of detecting issues that may affect or areaffecting the assets per the guidelines, system requirements, systemdesign, system build, and resulting system. The analysis system rendersone or more fourth evaluation ratings for the implementation andoperation of responding to issues that may affect or are affecting theassets per the guidelines, system requirements, system design, systembuild, and resulting system.

The analysis system renders one or more fifth evaluation ratings for theimplementation and operation of recovering from issues that may affector are affecting the assets per the guidelines, system requirements,system design, system build, and resulting system. The analysis systemmay render an overall evaluation rating for the implementation and/orperformance based on the one or more first through one or more fifthevaluation ratings.

FIG. 54 is a diagram of an example of system aspects, evaluationaspects, evaluation rating metrics, and analysis system output optionsof an analysis system 11 for analyzing a system 11, or portion thereof.For instance, analysis system 11 is evaluating the implementation forand operation of identifying assets of a department, protecting theassets from issues, detecting issues that may affect or are affectingthe assets, responding to issues that may affect or are affecting theassets, and recovering from issues that affected the assets per theguidelines, system requirements, system design, system build, andresulting system based on discovered data and desired data.

For this specific example, the analysis system 10 obtains disclosed dataand discovered from the system regarding the guidelines, systemrequirements, system design, system build, and resulting systemassociated with the assets of the department. From the discovered dataand desired data, the analysis system renders one or more firstevaluation ratings (e.g., one for each of guidelines, systemrequirements, system design, system build, resulting system with respectto each of implementation and operation or one for all of them) for theimplementation and operation of identifying the assets per theguidelines, system requirements, system design, system build, andresulting system. The analysis system renders one or more secondevaluation ratings for the implementation and operation of protectingthe assets from issues per the guidelines, system requirements, systemdesign, system build, and resulting system.

The analysis system renders one or more third evaluation ratings for theimplementation and operation of detecting issues that may affect or areaffecting the assets per the guidelines, system requirements, systemdesign, system build, and resulting system. The analysis system rendersone or more fourth evaluation ratings for the implementation andoperation of responding to issues that may affect or are affecting theassets per the guidelines, system requirements, system design, systembuild, and resulting system.

The analysis system renders one or more fifth evaluation ratings for theimplementation and operation of recovering from issues that may affector are affecting the assets per the guidelines, system requirements,system design, system build, and resulting system. The analysis systemmay render an overall evaluation rating for the implementation and/orperformance based on the one or more first through one or more fifthevaluation ratings.

The analysis system 11 may further render an implementation and/oroperation evaluation rating regarding how well the discovered datacorrelates with the desired data. In other words, evaluate the levelimplementation and operation of the system. In this example, theanalysis system compares the disclosed data with the desired data. Ifthey substantially match, the implementation and/or operation of thesystem would receive a relatively high evaluation rating. The more thediscovered data differs from the desired data, the lower theimplementation and/or operation evaluation rating will be.

FIG. 55 is a diagram of an example of system aspects, evaluationaspects, evaluation rating metrics, and analysis system output optionsof an analysis system 11 for analyzing a system 11, or portion thereof.For instance, analysis system 11 is evaluating the system'sself-evaluation for identifying assets, protecting the assets fromissues, detecting issues that may affect or are affecting the assets,responding to issues that may affect or are affecting the assets, andrecovering from issues that affected the assets of a department based ondisclosed data and discovered data per the guidelines, systemrequirements, and system design.

For this specific example, the analysis system 10 obtains disclosed dataand discovered from the system regarding the guidelines, systemrequirements, and system design associated with the assets of thedepartment. From the disclosed data and discovered, the analysis systemrenders one or more first evaluation ratings (e.g., one for each ofguidelines, system requirements, and system design, or one for allthree) for the self-evaluation of identifying assets per the guidelines,system requirements, and system design. For instance, what resourcesdoes the system have with respect to its guidelines, systemrequirements, and/or system design for self-identifying of assets.

The analysis system renders one or more second evaluation ratings forthe self-evaluation of protecting the assets from issues per theguidelines, system requirements, and system design regarding. Theanalysis system renders one or more third evaluation ratings for theself-evaluation of detecting issues that may affect or are affecting theassets per the guidelines, system requirements, and system designregarding detection.

The analysis system renders one or more fourth evaluation ratings forthe self-evaluation of responding to issues that may affect or areaffecting the assets per the guidelines, system requirements, and systemdesign. The analysis system renders one or more fifth evaluation ratingsfor the self-evaluation of recovering from issues that affected theassets per the guidelines, system requirements, and system design. Theanalysis system may render an overall evaluation rating for theself-evaluation based on the one or more first through one or more fifthevaluation ratings.

FIG. 56 is a diagram of an example of system aspects, evaluationaspects, evaluation rating metrics, and analysis system output optionsof an analysis system 11 for analyzing a system 11, or portion thereof.For instance, analysis system 11 is evaluating the understanding of theguidelines, system requirements, system design, system build, andresulting system for identifying assets, protecting the assets fromissues, detecting issues that may affect or are affecting the assets,responding to issues that may affect or are affecting the assets, andrecovering from issues that affected the assets of a department based ondisclosed data and discovered data.

For this specific example, the analysis system 10 obtains disclosed dataand discovered data from the system regarding guidelines, systemrequirements, system design, system build, and resulting systemassociated with the assets of the department. As a specific example, thedisclosed data includes guidelines that certain types of data shall beencrypted; a system requirement that specifies 128-bit AdvancedEncryption Standard (AES) for “y” types of documents; a system designthat includes 12 “x” type computers that are to be loaded with 128-bitAES software by company “M”, version 2.0 or newer; and a system buildand resulting system that includes 12 “x” type computers that have128-bit AES software by company “M”, version 2.1.

For this specific example, the discovered data includes the sameguideline as the disclosed data; a first system requirement thatspecifies 128-bit Advanced Encryption Standard (AES) for “y” types ofdocuments and a second system requirement that specifies 256-bitAdvanced Encryption Standard (AES) for “A” types of documents; a systemdesign that includes 12 “x” type computers that are to be loaded with128-bit AES software by company “M”, version 2.0 or newer, and 3 “z”type computers that are to be loaded with 256-bit AES software bycompany “N” version 3.0 or newer; and a system build and resultingsystem that includes 10 “x” type computers that have 128-bit AESsoftware by company “M” version 2.1, 2 “x” type computers that have128-bit AES software by company “M” version 1.3, 2 “z” type computersthat have 256-bit AES software by company “N” version 3.1, and 1 “z”type computer that has 256-bit AES software by company “K” version 0.1.

From just the disclosed data, the analysis system would render arelatively high evaluation rating for the understanding of theguidelines, system requirements, system design, system build, andresulting system associated with the assets of the department. Therelatively high evaluation rating would be warranted since the systembuild and resulting system included what was in the system design (e.g.,12 “x” type computers that have 128-bit AES software by company “M”,version 2.1). Further, the system design is consistent with the systemreequipments (e.g., 128-bit Advanced Encryption Standard (AES) for “y”types of documents), which is consistent with the guidelines (e.g.,certain types of data shall be encrypted).

From the discovered data, however, the analysis system would render arelatively low evaluation rating for the understanding of theguidelines, system requirements, system design, system build, andresulting system associated with the assets of the department. Therelatively low evaluation rating would be warranted since the systembuild and resulting system is not consistent with the system design(e.g., is missing 2 “x” type computers with the right encryptionsoftware, only has 2 “z” type computers with the right software, and hasa “z” type computer with the wrong software).

The analysis system would also process the evaluation ratings from thedisclosed data and from the discovered data to produce an overallevaluation rating for the understanding of the guidelines, systemrequirements, system design, system build, and resulting systemassociated with the assets of the department. In this instance, thedisclosed data does not substantially match the discovered data, whichindicates a lack of understanding of what's really in the system (i.e.,knowledge of the system). Further, since the evaluation rating from thediscovered data was low, the analysis system would produce a low overallevaluation rating for the understanding.

FIG. 57 is a diagram of an extension of the example of FIG. 56 . In thisexample, the analysis system processes the data and/or evaluationratings to identify deficiencies and/or auto-corrections of at leastsome of the deficiencies. As shown, the disclosed data includes:

-   -   guidelines that certain types of data shall be encrypted;    -   a system requirement that specifies 128-bit Advanced Encryption        Standard (AES) for “y” types of documents;    -   a system design that includes 12 “x” type computers that are to        be loaded with 128-bit AES software by company “M”, version 2.0        or newer; and    -   a system build and resulting system that includes 12 “x” type        computers that have 128-bit AES software by company “M”, version        2.1.

As is also shown, the discovered data includes:

-   -   the same guideline as the disclosed data;    -   a first system requirement that specifies 128-bit Advanced        Encryption Standard (AES) for “y” types of documents and a        second system requirement that specifies 256-bit Advanced        Encryption Standard (AES) for “A” types of documents;    -   a system design that includes 12 “x” type computers that are to        be loaded with 128-bit AES software by company “M”, version 2.0        or newer, and 3 “z” type computers that are to be loaded with        256-bit AES software by company “N”, version 3.0 or newer; and    -   a system build and resulting system that includes:    -   10 “x” type computers that have 128-bit AES software by company        “M”, version 2.1;    -   2 “x” type computers that have 128-bit AES software by company        “M”, version 1.3;    -   2 “z” type computers that have 256-bit AES software by company        “N”, version 3.1; and    -   1 “z” type computer that has 256-bit AES software by company        “K”, version 0.1.

From this data, the analysis system identifies deficiencies 232 and,when possible, provides auto-corrections 235. For example, the analysissystem determines that the system requirements also included arequirement for 256-bit AES for “A” type documents. The analysis systemcan auto-correct this deficiency by updating the knowledge of the systemto include the missing requirement. This may include updating one ormore policies, one or more processes, one or more procedures, and/orupdating documentation.

As another example, the analysis system identifies the deficiency of thedesign further included 3 “z” type computers that are to be loaded with256-bit AES software by company “N”, version 3.0 or newer. The analysissystem can auto-correct this deficiency by updating the knowledge of thesystem to include the 3 “z” type computers with the correct software.Again, this may include updating one or more policies, one or moreprocesses, one or more procedures, and/or updating documentation.

As another example, the analysis system identifies the deficiency of 2“x” type computers having old versions of the encryption software (e.g.,have version 1.3 of company M's 128-bit AES software instead of aversion 2.0 or newer). The analysis system can auto-correct thisdeficiency by updating the version of software for the two computers.

As another example, the analysis system identifies the deficiency of 1“z” type computer has the wrong encryption software (e.g., it hasversion 0.1 from company K and not version 3.0 or newer from company N).The analysis system can auto-correct this deficiency by replacing thewrong encryption software with the correct encryption software.

As another example, the analysis system identifies the deficiency of 1“z” type computer is missing from the system. The analysis system cannotauto-correct this deficiency since it is missing hardware. In thisinstance, the analysis system notifies a system admin of the missingcomputer.

FIG. 58 is a schematic block diagram of an embodiment of an evaluationprocessing module 254 that includes a plurality of comparators 360-362,a plurality of analyzers 363-365, and a deficiency correction module366. In general, the evaluation processing module 254 identifiesdeficiencies 232 and, when possible, determines auto-corrections 235from the ratings 219 and/or inputted data (e.g., disclosed data,discovered data, and/or desired data) based on evaluation parameters 266(e.g., disclosed to discovered deficiency criteria 368, discovered todesired deficiency criteria 370, disclosed to desired deficiencycriteria 372, disclosed to discovered compare criteria 373, discoveredto desired compare criteria 374, and disclosed to desired comparecriteria 375).

In an example, comparator 360 compares disclosed data and/or ratings 338and discovered data and/or ratings 339 based on the disclosed todiscovered compare criteria 373 to produce, if any, one or moredisclosed to discovered differences 367. As a more specific example, theanalysis system evaluates disclosed, discovered, and/or desired data toproduce one or more evaluation ratings regarding the understanding ofthe guidelines, system requirements, system design, system build, andresulting system associated with identifying the assets of thedepartment.

Each of the disclosed data, discovered data, and desired data includesdata regarding the guidelines, system requirements, system design,system build, and/or resulting system associated with identifying theassets of the department and/or the assets of the department. Recallthat disclosed data is the known data of the system at the outset of ananalysis, which is typically supplied by a system administrator and/oris obtained from data files of the system. The discovered data is thedata discovered about the system by the analysis system during theanalysis. The desired data is the data obtained by the analysis systemfrom system proficiency resources regarding desired guidelines, systemrequirements, system design, system build, and/or system operation.

For the understanding of the guidelines, system requirements, systemdesign, system build, and resulting system associated with identifyingthe assets of the department, the analysis system may produce one ormore evaluation ratings. For example, the analysis system produces anevaluation rating for:

-   -   understanding of the guidelines with respect to identifying        assets of the department from the disclosed data;    -   understanding of the guidelines with respect to identifying        assets of the department from the discovered data;    -   understanding of the guidelines with respect to identifying        assets of the department from the desired data;    -   understanding of the system requirements with respect to        identifying assets of the department from the disclosed data;    -   understanding of the system requirements with respect to        identifying assets of the department from the discovered data;    -   understanding of the system requirements with respect to        identifying assets of the department from the desired data;    -   understanding of the system design with respect to identifying        assets of the department from the disclosed data;    -   understanding of the system design with respect to identifying        assets of the department from the discovered data;    -   understanding of the system design with respect to identifying        assets of the department from the desired data;    -   understanding of the system build with respect to identifying        assets of the department from the disclosed data;    -   understanding of the system build with respect to identifying        assets of the department from the discovered data;    -   understanding of the system build with respect to identifying        assets of the department from the desired data;    -   understanding of the resulting system with respect to        identifying assets of the department from the disclosed data;    -   understanding of the resulting system with respect to        identifying assets of the department from the discovered data;    -   understanding of the resulting system with respect to        identifying assets of the department from the desired data;        and/or    -   an overall understanding of identifying the assets of the        department.

The disclosed to discovered compare criteria 373 specifies theevaluation ratings to be compared and/or which data of the discloseddata is to be compared to data of the discovered data. For example, thedisclosed to discovered compare criteria 373 indicates that the“understanding of the guidelines with respect to system design of thedepartment from the disclosed data” is to be compared to the“understanding of the system design with respect to identifying assetsof the department from the discovered data”. As another example, thedisclosed to discovered compare criteria 373 indicates that dataregarding system design of the disclosed data is to be compared with thedata regarding the system design of the discovered data.

In accordance with the disclosed to discovered compare criteria 373 andfor this specific example, the comparator 360 compares the“understanding of the guidelines with respect to system design of thedepartment from the disclosed data” with the “understanding of thesystem design with respect to identifying assets of the department fromthe discovered data” to produce, if any, one or more understandingdifferences. The comparator 360 also compares the data regarding systemdesign of the disclosed data with the data regarding the system designof the discovered data to produce, if any, one or more data differences.The comparator 360 outputs the one or more understanding differencesand/or the one or more data differences as the disclosed to discovereddifferences 367.

The analyzer 363 analyzes the disclosed to discovered differences 267 inaccordance with the disclosed to discovered deficiency criteria 368 todetermine whether a difference 267 constitutes a deficiency. If so, theanalyzer 363 includes it in the disclosed to discovered deficiencies232-1. The disclosed to discovered deficiency criteria 368 correspond tothe disclosed to discovered compare criteria 373 and specify how thedifferences 367 are to be analyzed to determine if they constitutedeficiencies 232-1.

As an example, the disclosed to discovered deficiency criteria 368specify a series of comparative thresholds based on the impact thedifferences have on the system. The range of impact is from none tosignificant with as many granular levels in between as desired. Fordifferences that have a significant impact on the system, thecomparative threshold is set to trigger a deficiency for virtually anydifference. For example, if the difference is regarding system security,then then threshold is set that any difference is a deficiency.

As another example, if the difference is regarding is inconsequentialinformation, then the threshold is set to not identify the difference asa deficiency. For example, the discovered data includes a PO date onNov. 2, 2020 for a specific purchase order and the disclosed data didn'tinclude a PO date, but the rest of the information regarding the PO isthe same for the disclosed and discovered data. In this instance, themissing PO date is inconsequential and would not be identified as adeficiency.

The deficiency correction module 366 receives the disclosed todiscovered deficiencies 232-1, if any, and determines whether one ormore of the deficiencies 232-1 can be auto-corrected to produce anauto-correction 235. In many instances, software deficiencies areauto-correctable (e.g., wrong software, missing software, out-of-datesoftware, etc.) while hardware deficiencies are not auto-correctable(e.g., wrong computing device, missing computing device, missing networkconnection, etc.).

The comparator 361 functions similarly to the comparator 360 to producediscovered to desired differences 369 based on the discovered dataand/or rating 339 and the desired data and/or rating 340 in accordancewith the discovered to desired compare criteria 374. The analyzer 364functions similarly to the analyzer 363 to produce discovered to desireddeficiencies 232-2 from the discovered to desired differences 369 inaccordance with the discovered to desired deficiency criteria 370. Thedeficiency correction module 366 auto-corrects, when possible, thediscovered to desired deficiencies 232-2 to produce auto-corrections235.

The comparator 362 functions similarly to the comparator 360 to producedisclosed to desired differences 371 based on the disclosed data and/orrating 338 and the desired data and/or rating 340 in accordance with thedisclosed to desired compare criteria 375. The analyzer 365 functionssimilarly to the analyzer 363 to produce disclosed to desireddeficiencies 232-3 from the disclosed to desired differences 371 inaccordance with the disclosed to desired deficiency criteria 372. Thedeficiency correction module 366 auto-corrects, when possible, thedisclosed to desired deficiencies 232-3 to produce auto-corrections 235.

While the examples were for the understanding of the system with respectto identifying assets of the department, the evaluation processingmodule 254 processes any combination of system aspects, evaluationaspects, and evaluation metrics in a similar manner. For example, theevaluation processing module 254 processes the implementation of thesystem with respect to identifying assets of the department to identifydeficiencies 232 and auto-corrections in the implementation. As anotherexample, the evaluation processing module 254 processes the operation ofthe system with respect to identifying assets of the department toidentify deficiencies 232 and auto-corrections in the operation of thesystem.

FIG. 59 is a state diagram of an example the analysis system analyzing asystem. From a start state 380, the analysis proceeds to anunderstanding of the system state 38) or to a test operations of theassets system functions, and/or security functions of a system state 386based on the desired analysis to be performed. For testing theunderstanding, the analysis proceeds to state 381 where theunderstanding of the assets, system functions, and/or security functionsof the system are evaluated. This may be done via documentation of thesystem, policies of the supported business, based upon a question andanswer session with personnel of the owner/operator of the system,and/or as discussed herein.

If the understanding of the system is inadequate, the analysis proceedsto the determine deficiencies in the understanding of the system state382. In this state 382, the deficiencies in understanding are determinedby processing differences and/or as discussed herein.

From state 382, corrections required in understanding the system areidentified and operation proceeds to state 383 in which a report isgenerated regarding understanding deficiencies and/or correctivemeasures to be taken. In addition, a report is generated and sent to theowner/operator of the other system. If there are no understandingdeficiencies and/or corrective measures, no auto correction is needed,and operations are complete at the done state.

If an autocorrect can be done, operation proceeds to state 384 where theanalysis system updates a determined ability to understand the othersystem. Corrections are then implemented, and operation proceeds back tostate 381. Note that corrections may be automatically performed for somedeficiencies but not others, depending upon the nature of thedeficiency.

From state 381, if the tested understanding of the system is adequate,operation proceeds to state 385 where a report is generated regarding anadequate understanding of the system and the report is sent. From state385 if operation is complete, operations proceed to the done state.Alternately, from state 385 operation may proceed to state 386 wheretesting of the assets, system functions and/or security functions of theother system is performed. If testing of the assets, system functions,and/or security functions of the system results in an adequate testresult, operation proceeds to state 390 where a report is generatedindicating adequate implementation and/or operation of the system andthe report is sent.

Alternately, at state 386 if the testing of the system results in aninadequate result, operations proceed to state 387 where deficiencies inthe assets, system functions, and/or security functions of the systemare tested. At state 387 differences are compared to identifydeficiencies in the assets, system functions, and/or security functions.The analysis then proceeds from state 387 to state 388 where a report isgenerated regarding corrective measures to be taken in response to theassets, system functions, and/or security functions deficiencies. Thereport is then sent to the owner/operator. If there are no deficienciesand/or corrective measures, no auto correction is needed, and operationsare complete at the done state. If autocorrect is required, operationproceeds to state 389 where the analysis system updates assets, systemfunctions, and/or security functions of the system. Corrections are thenimplemented and the analysis proceeds to state 386. Note thatcorrections may be automatically performed for some deficiencies but notothers, depending upon the nature of the deficiency.

FIG. 60 is a logic diagram of an example of an analysis system analyzinga system, or portion thereof. The method includes the analysis systemobtaining system proficiency understanding data regarding the assets ofthe system (step 400) and obtaining data regarding the owner/operator'sunderstanding of the assets (step 401). System proficiencies of step 400include industry best practices and regulatory requirements, forexample. The data obtained from the system at step 401 is based upondata received regarding the system or received by probing the system.

The data collected at steps 400 and 401 is then compared (step 402) anda determination is made regarding the comparison. If the comparison isfavorable, as determined at step 403, meaning that the systemproficiency understanding compares favorably to the data regardingunderstanding, operation is complete, a report is generated (step 412),and the report is sent (step 413). If the comparison is not favorable,as determined at step 403, operation continues with identifyingdeficiencies in the understanding of the system (step 404), identifyingcorrective measures (step 405), generating a corresponding report (step412) and sending the report (step 413).

The method also includes the analysis system obtaining systemproficiency understanding data of the system functions and/or securityimplementation and/or operation of the system (step 406) and obtainingdata regarding the owner/operator's understanding of the systemfunctions and/or security functions implementation and/or operation ofthe system (step 407). System proficiencies of step 406 include industrybest practices and regulatory requirements, for example. The dataobtained from the system at step 407 is based upon data receivedregarding the system or received by probing the system.

The data collected at steps 406 and 407 is then compared (step 414) anda determination is made regarding the comparison. If the comparison isfavorable, as determined at step 415, meaning that the systemproficiency understanding compares favorably to the data regardingunderstanding, operation is complete, a report is generated (step 412),and the report is sent (step 413). If the comparison is not favorable,as determined at step 415, operation continues with identifyingdeficiencies in the understanding of the system (step 416), identifyingcorrective measures (step 417), generating a corresponding report (step412) and sending the report (step 413).

The method further includes the analysis system comparing theunderstanding of the physical structure (obtained at step 401) with theunderstanding of the system functions and/or security functionsimplementation and/or operation (obtained at step 406) at step 408. Step408 essentially determines whether the understanding of the assetscorresponds with the understanding of the system functions and/orsecurity functions of the implementation and/or operation of the system.If the comparison is favorable, as determined at step 409, a report isgenerated (step 412), and the report is sent (step 413). If thecomparison is not favorable, as determined at step 409, the methodcontinues with identifying imbalances in the understanding (step 410),identifying corrective measures (step 410), generating a correspondingreport (step 412), and sending the report (step 413).

FIG. 61 is a logic diagram of another example of an analysis systemanalyzing a system, or portion thereof. The method begins at step 420where the analysis system determines a system evaluation mode (e.g.,assets, system functions, and/or security functions) for analysis. Themethod continues at step 421 where the analysis system determines asystem evaluation level (e.g., the system or a portion thereof). Forinstance, the analysis system identifies one or more system elements forevaluation.

The method continues at step 422 where the analysis system determines ananalysis perspective (e.g., understanding, implementation, operation,and/or self-evaluate). The method continues at step 423 where theanalysis system determines an analysis viewpoint (e.g., disclosed,discovered, and/or desired). The method continues at step 424 where theanalysis system determines a desired output (e.g., evaluation rating,deficiencies, and/or auto-corrections).

The method continues at step 425 where the analysis system determineswhat data to gather based on the preceding determinations. The methodcontinues at step 426 where the analysis system gathers data inaccordance with the determination made in step 425. The method continuesat step 427 where the analysis system determines whether the gathereddata is to be pre-processed.

If yes, the method continues at step 428 where the analysis systemdetermines data pre-processing functions (e.g., normalize, parse, tag,and/or de-duplicate). The method continues at step 429 where theanalysis system pre-processes the data based on the pre-processingfunctions to produce pre-processed data. Whether the data ispre-processed or not, the method continues at step 430 where theanalysis system determines one or more evaluation categories (e.g.,identify, protect, detect, respond, and/or recover) and/orsub-categories for evaluation. Note that this may be done prior to step425 and be part of determining the data to gather.

The method continues at step 431 where the analysis system analyzes thedata in accordance with the determine evaluation categories and inaccordance with a selected evaluation metric (e.g., process, policy,procedure, automation, certification, and/or documentation) to produceanalysis results. The method continues at step 432 where the analysissystem processes the analysis results to produce the desired output(e.g., evaluation rating, deficiencies, and/or auto-correct). The methodcontinues at step 432 where the analysis system determines whether toend the method or repeat it for another analysis of the system.

FIG. 62 is a logic diagram of another example of an analysis systemanalyzing a system or portion thereof. The method begins at step 440where the analysis system determines physical assets of the system, orportion thereof, to analyze (e.g., assets in the resulting system).Recall that a physical asset is a computing entity, a computing device,a user software application, a system software application (e.g.,operating system, etc.), a software tool, a network softwareapplication, a security software application, a system monitoringsoftware application, and the like.

The method continues at step 441 where the analysis system ascertainsimplementation of the system, or portion thereof (e.g., assets designedto be, and/or built, in the system). The method continues at step 442where the analysis system correlates components of the assets tocomponents of the implementation (e.g., do the assets of the actualsystem correlate with assets design/built to be in the system).

The method continues at step 443 where the analysis system scores thecomponents of the physical assets in accordance with the mappedcomponents of the implementation. For example, the analysis systemscores how well the assets of the actual system correlate with assetsdesign/built to be in the system. The scoring may be based on one ormore evaluation metrics (e.g. process, policy, procedure, automation,certification, and/or documentation). The method continues at step 444where the analysis system performs a function on the scores to obtain aresult (e.g., an evaluation rating, identified deficiencies, and/orauto-correction of deficiencies).

The method continues at step 445 where the analysis system determineswhether the result is equal or greater than a target result (e.g., theevaluation rating is a certain value). If yes, the method continues atstep 446 where the analysis system indicates that the system, or portionthereof, passes this particular test. If the results are less than thetarget result, the method continues at step 447 where the analysissystem identifies vulnerabilities in the physical assets and/or in theimplementation. For example, the analysis system determines that asecurity software application is missing from several computing devicesin the system, or portion thereof, being analyzed.

The method continues at step 448 where the analysis system determines,if possible, corrective measures of the identified vulnerabilities. Themethod continues at step 449 where the analysis system determineswhether the corrective measures can be done automatically. If not, themethod continues at step 451 where the analysis system reports thecorrective measures. If yes, the method continues at step 450 where theanalysis system auto-corrects the vulnerabilities.

FIG. 63 is a logic diagram of another example of an analysis systemanalyzing a system or portion thereof. The method begins at step 460where the analysis system determines physical assets of the system, orportion thereof, to analyze (e.g., assets and their intended operation).The method continues at step 461 where the analysis system ascertainsoperation of the system, or portion thereof (e.g., the operationsactually performed by the assets). The method continues at step 462where the analysis system correlates components of the assets tocomponents of operation (e.g., do the identified operations of theassets correlate with the operations actually performed by the assets).

The method continues at step 463 where the analysis system scores thecomponents of the physical assets in accordance with the mappedcomponents of the operation. For example, the analysis system scores howwell the identified operations of the assets correlate with operationsactually performed by the assets. The scoring may be based on one ormore evaluation metrics (e.g. process, policy, procedure, automation,certification, and/or documentation). The method continues at step 464where the analysis system performs a function on the scores to obtain aresult (e.g., an evaluation rating, identified deficiencies, and/orauto-correction of deficiencies).

The method continues at step 465 where the analysis system determineswhether the result is equal or greater than a target result (e.g., theevaluation rating is a certain value). If yes, the method continues atstep 466 where the analysis system indicates that the system, or portionthereof, passes this particular test. If the results are less than thetarget result, the method continues at step 467 where the analysissystem identifies vulnerabilities in the physical assets and/or in theoperation.

The method continues at step 468 where the analysis system determines,if possible, corrective measures of the identified vulnerabilities. Themethod continues at step 469 where the analysis system determineswhether the corrective measures can be done automatically. If not, themethod continues at step 471 where the analysis system reports thecorrective measures. If yes, the method continues at step 470 where theanalysis system auto-corrects the vulnerabilities.

FIG. 64 is a logic diagram of another example of an analysis systemanalyzing a system or portion thereof. The method begins at step 480where the analysis system determines system functions of the system, orportion thereof, to analyze. The method continues at step 481 where theanalysis system ascertains implementation of the system, or portionthereof (e.g., system functions designed to be, and/or built, in thesystem). The method continues at step 482 where the analysis systemcorrelates components of the system functions to components of theimplementation (e.g., do the system functions of the actual systemcorrelate with system functions design/built to be in the system).

The method continues at step 483 where the analysis system scores thecomponents of the system functions in accordance with the mappedcomponents of the implementation. For example, the analysis systemscores how well the system functions of the actual system correlate withsystem functions design/built to be in the system. The scoring may bebased on one or more evaluation metrics (e.g. process, policy,procedure, automation, certification, and/or documentation). The methodcontinues at step 484 where the analysis system performs a function onthe scores to obtain a result (e.g., an evaluation rating, identifieddeficiencies, and/or auto-correction of deficiencies).

The method continues at step 485 where the analysis system determineswhether the result is equal or greater than a target result (e.g., theevaluation rating is a certain value). If yes, the method continues atstep 486 where the analysis system indicates that the system, or portionthereof, passes this particular test. If the results are less than thetarget result, the method continues at step 487 where the analysissystem identifies vulnerabilities in the physical assets and/or in theimplementation.

The method continues at step 488 where the analysis system determines,if possible, corrective measures of the identified vulnerabilities. Themethod continues at step 489 where the analysis system determineswhether the corrective measures can be done automatically. If not, themethod continues at step 491 where the analysis system reports thecorrective measures. If yes, the method continues at step 490 where theanalysis system auto-corrects the vulnerabilities.

FIG. 65 is a logic diagram of another example of an analysis systemanalyzing a system or portion thereof. The method begins at step 500where the analysis system determines system functions of the system, orportion thereof, to analyze. The method continues at step 501 where theanalysis system ascertains operation of the system, or portion thereof(e.g., the operations associated with the system functions). The methodcontinues at step 502 where the analysis system correlates components ofthe system functions to components of operation (e.g., do the identifiedoperations of the system functions correlate with the operationsactually performed to provide the system functions).

The method continues at step 503 where the analysis system scores thecomponents of the system functions in accordance with the mappedcomponents of the operation. For example, the analysis system scores howwell the identified operations to support the system functions correlatewith operations actually performed to support the system functions. Thescoring may be based on one or more evaluation metrics (e.g. process,policy, procedure, automation, certification, and/or documentation). Themethod continues at step 504 where the analysis system performs afunction on the scores to obtain a result (e.g., an evaluation rating,identified deficiencies, and/or auto-correction of deficiencies).

The method continues at step 505 where the analysis system determineswhether the result is equal or greater than a target result (e.g., theevaluation rating is a certain value). If yes, the method continues atstep 506 where the analysis system indicates that the system, or portionthereof, passes this particular test. If the results are less than thetarget result, the method continues at step 507 where the analysissystem identifies vulnerabilities in the physical assets and/or in theoperation.

The method continues at step 508 where the analysis system determines,if possible, corrective measures of the identified vulnerabilities. Themethod continues at step 509 where the analysis system determineswhether the corrective measures can be done automatically. If not, themethod continues at step 511 where the analysis system reports thecorrective measures. If yes, the method continues at step 510 where theanalysis system auto-corrects the vulnerabilities.

FIG. 66 is a logic diagram of another example of an analysis systemanalyzing a system or portion thereof. The method begins at step 520where the analysis system determines security functions of the system,or portion thereof, to analyze. The method continues at step 521 wherethe analysis system ascertains implementation of the system, or portionthereof (e.g., security functions designed to be, and/or built, in thesystem). The method continues at step 522 where the analysis systemcorrelates components of the security functions to components of theimplementation (e.g., do the security functions of the actual systemcorrelate with security functions design/built to be in the system).

The method continues at step 523 where the analysis system scores thecomponents of the security functions in accordance with the mappedcomponents of the implementation. For example, the analysis systemscores how well the security functions of the actual system correlatewith security functions design/built to be in the system. The scoringmay be based on one or more evaluation metrics (e.g. process, policy,procedure, automation, certification, and/or documentation). The methodcontinues at step 524 where the analysis system performs a function onthe scores to obtain a result (e.g., an evaluation rating, identifieddeficiencies, and/or auto-correction of deficiencies).

The method continues at step 525 where the analysis system determineswhether the result is equal or greater than a target result (e.g., theevaluation rating is a certain value). If yes, the method continues atstep 526 where the analysis system indicates that the system, or portionthereof, passes this particular test. If the results are less than thetarget result, the method continues at step 527 where the analysissystem identifies vulnerabilities in the physical assets and/or in theimplementation.

The method continues at step 528 where the analysis system determines,if possible, corrective measures of the identified vulnerabilities. Themethod continues at step 529 where the analysis system determineswhether the corrective measures can be done automatically. If not, themethod continues at step 531 where the analysis system reports thecorrective measures. If yes, the method continues at step 530 where theanalysis system auto-corrects the vulnerabilities.

FIG. 67 is a logic diagram of another example of an analysis systemanalyzing a system or portion thereof. The method begins at step 540where the analysis system determines security functions of the system,or portion thereof, to analyze. The method continues at step 541 wherethe analysis system ascertains operation of the system, or portionthereof (e.g., the operations associated with the security functions).The method continues at step 542 where the analysis system correlatescomponents of the security functions to components of operation (e.g.,do the identified operations of the security functions correlate withthe operations actually performed to provide the security functions).

The method continues at step 543 where the analysis system scores thecomponents of the security functions in accordance with the mappedcomponents of the operation. For example, the analysis system scores howwell the identified operations to support the security functionscorrelate with operations actually performed to support the securityfunctions. The scoring may be based on one or more evaluation metrics(e.g. process, policy, procedure, automation, certification, and/ordocumentation). The method continues at step 544 where the analysissystem performs a function on the scores to obtain a result (e.g., anevaluation rating, identified deficiencies, and/or auto-correction ofdeficiencies).

The method continues at step 545 where the analysis system determineswhether the result is equal or greater than a target result (e.g., theevaluation rating is a certain value). If yes, the method continues atstep 546 where the analysis system indicates that the system, or portionthereof, passes this particular test. If the results are less than thetarget result, the method continues at step 547 where the analysissystem identifies vulnerabilities in the physical assets and/or in theoperation.

The method continues at step 548 where the analysis system determines,if possible, corrective measures of the identified vulnerabilities. Themethod continues at step 549 where the analysis system determineswhether the corrective measures can be done automatically. If not, themethod continues at step 551 where the analysis system reports thecorrective measures. If yes, the method continues at step 550 where theanalysis system auto-corrects the vulnerabilities.

FIG. 68 is a logic diagram of an example of an analysis systemgenerating an evaluation output. The method begins at step 560 where ananalysis unit of the analysis system obtains (e.g., receives, gathers,inputs, and/or other means) a collection of data for a particularevaluation of a system aspect (e.g., what is being evaluated withrespect to one or more system elements, one or more system criteria,and/or one or more system modes). The particular evaluation indicateshow to evaluate the system aspect by specifying an evaluation aspect,indicates a manner of evaluation by specifying one or more evaluationmetrics, indicates an evaluation output.

The method continues at step 561 where the analysis unit acquires (e.g.,receives, generates, determines, and/or other means) data analysisparameters regarding the particular evaluation of the system aspect. Anexample of data analysis parameters were discussed with reference toFIG. 35 and other examples will be discussed with reference to one ormore of 89-138.

The method continues at step 562 where the analysis unit determines oneor more evaluation perspectives based on the data analysis parameters.An evaluation perspective is understanding (e.g., knowledge and/orintent of system), implementation (e.g., how the system was developed),operation (e.g., how the system fulfills its objectives), orself-analysis (e.g., the system's self-protecting, self-healing, etc.).

The method continues at step 563 where the analysis unit determines oneor more evaluation modalities based on the data analysis parameters. Anevaluation modality is sufficiency, effectiveness, a measure of use, ameasure of appropriate of use, or a measure of consistency of use.Sufficiency is regarding an adequate quantity of data for an evaluationmetric (e.g., process, policy, procedure, documentation, certification,and/or automation) associated with the system aspect. Effectiveness isregarding adequate content of the data of an evaluation metric withrespect to one or more objectives of the system aspect. The measure ofuse is regarding the quantity of use of the data of an evaluation metricwith respect to supporting the one or more objectives of the systemaspect. The measure of appropriate use is regarding the conditions ofuse of the data of an evaluation metric with respect to supporting theone or more objectives of the system aspect. The measure of consistencyof use is regarding the situations of use of data of the evaluationmetric with respect to supporting the one or more objectives of thesystem aspect.

The method continues at step 564 where the analysis unit determines oneor more evaluation metrics based on the data analysis parameters. Anevaluation metric is one or more processes, one or more policies, one ormore procedures; one or more documents, one or more automations, or oneor more certifications. The method may further include the analysis unitdetermining one or more evaluation viewpoints based on the data analysisparameters. An evaluation viewpoint is a disclosed data viewpoint, adiscovered data viewpoint, or a desired data viewpoint.

The method continues at step 565 where the analysis unit evaluates thecollection of data in accordance with the one or more evaluationmetrics, the one or more evaluation perspectives, and the one or moreevaluation modalities to produce one or more evaluation outputs. Anevaluation output is one or more evaluation ratings, one or more systemaspect deficiencies, or one or more auto-corrections of the one or moresystem aspect deficiencies.

FIG. 69 is a logic diagram of a further example of an analysis systemgenerating an evaluation output when the evaluation modality is asufficiency modality. The method includes step 566 where the analysisunit quantifies (e.g., counts, verifies via a checklist, or other means)data of the collection of data regarding an evaluation metric to producequantified data. The method continues at step 567 where the analysisunit determines a reference scale based on an evaluation perspective(e.g., understanding, implementation, operation, and/or self-analysis)of the system aspect for the evaluation metric.

The method continues at step 568 where the analysis unit compares thequantified data with the reference scale to produce an evaluation ratingregarding sufficiency of the evaluation metric for the system aspectfrom the evaluation perspective. In general terms, the sufficiencymodality is an evaluation as to whether there are enough policies,processes, procedures, documentation, automation, and/or certificationsto support the objectives of the system aspect. Examples of this methodwill be discussed with reference to one or more subsequent figures.

FIG. 70 is a logic diagram of a further example of an analysis systemgenerating an evaluation output when the evaluation modality is aneffectiveness modality. The method includes step 569 where the analysisunit determines a reference scale based on an evaluation perspective(e.g., understanding, implementation, operation, or self-analysis) ofthe one or more evaluation perspectives and one or more objectives ofthe system aspect for an evaluation metric. The method continues at step570 where the analysis unit evaluates data of the collection of dataregarding the evaluation metric with respect to the reference scale toproduce an evaluation rating regarding how effective the evaluationmetric supports the one or more objectives of the system aspect from theevaluation perspective.

In general terms, the effectiveness modality is an evaluation as towhether the system's policies, processes, procedures, documentation,automation, and/or certifications are effective at supporting theobjectives of the system aspect from the evaluation perspective.Examples of this method will be discussed with reference to one or moresubsequent figures.

FIG. 71 is a logic diagram of a further example of an analysis systemgenerating an evaluation output when the evaluation modality is ameasure of use modality. The method includes step 571 where the analysisunit determines a reference scale based on an evaluation perspective ofthe one or more evaluation perspectives and one or more objectives ofthe system aspect for an evaluation metric. The method continues at step572 where the analysis unit evaluates data of the collection of dataregarding the evaluation metric with respect to the reference scale toproduce an evaluation rating regarding quantity of use of the evaluationmetric to support the one or more objectives of the system aspect fromthe evaluation perspective.

In general terms, the measure of use modality is an evaluation as towhether the quantity of use of the system's policies, processes,procedures, documentation, automation, and/or certifications is adequate(e.g., about right amount of use expected for such a system) to supportthe objectives of the system aspect from the evaluation perspective.

FIG. 72 is a logic diagram of a further example of an analysis systemgenerating an evaluation output when the evaluation modality is ameasure of appropriate use modality. The method includes step 573 wherethe analysis unit determines a reference scale based on an evaluationperspective of the one or more evaluation perspectives and one or moreobjectives of the system aspect for an evaluation metric. The methodcontinues at step 574 where the analysis unit evaluates data of thecollection of data regarding the evaluation metric with respect to thereference scale to produce an evaluation rating regarding appropriateuse of the evaluation metric to support the one or more objectives ofthe system aspect from the evaluation perspective.

In general terms, the measure of appropriate use modality is anevaluation as to whether the conditions of use of the system's policies,processes, procedures, documentation, automation, and/or certificationsis appropriate (e.g., used when expected and not used when not expected)to support the objectives of the system aspect from the evaluationperspective.

FIG. 73 is a logic diagram of a further example of an analysis systemgenerating an evaluation output when the evaluation modality is ameasure of consistency of use modality. The method includes step 575where the analysis unit determines a reference scale based on anevaluation perspective of the one or more evaluation perspectives andone or more objectives of the system aspect for an evaluation metric.The method continues at step 576 where the analysis unit evaluates dataof the collection of data regarding the evaluation metric with respectto the reference scale to produce an evaluation rating regardingconsistency of use of the evaluation metric to support the one or moreobjectives of the system aspect from the evaluation perspective.

In general terms, the measure of consistency of use modality is anevaluation as to whether the situations of use of the system's policies,processes, procedures, documentation, automation, and/or certificationsis appropriate (e.g., always used of a given situation and never usedfor a different given situation) to support the objectives of the systemaspect from the evaluation perspective.

FIG. 74 is a diagram of an example of an analysis system generating anevaluation output for a selected portion of a system. In this example,the analysis system has three high-level tasks: (1) select a systemportion (e.g., system aspect or system sector); (2) determine what'sbeing evaluated for the selected system portion; and (3) determine thelevel of evaluation to produce an evaluation output. In an example, theanalysis system receives inputs to select the system portion, todetermine what's being evaluated, and/or to determine the level ofevaluation. In another example, the analysis system selects the systemportion, determines what's being evaluated, and/or determines the levelof evaluation based on the system under test.

In an embodiment, the system portion is selected based on an identifier.For example, the identifier identifies the entire system as the systemportion to be evaluated. As another example, the identifier identifiesthe system portion based on a division of the organization operating thesystem. As yet another example, the identifier identifies the systemportion based on a department of a division of the organizationoperating the system. As yet another example, the identifier identifiesthe system portion based on a group of a department of a division of theorganization operating the system. As yet another example, theidentifier identifies the system portion based on a sub-group of a groupof a department of a division of the organization operating the system.

As a further example, the identifier identifies one or more systemassets of the system to be the system portion. As a still furtherexample, the identifier identifies one or more system elements of thesystem to be the system portion, where a system element includes one ormore system assets and a system asset is one or more physical assetsand/or one or more conceptual assets. As a still further example, theidentifier identifies one or more physical assets of the system to bethe system portion. As a still further example, the identifieridentifies one or more system functions of the system to be the systemportion. As a still further example, the identifier identifies one ormore security functions of the system to be the system portion.

Having identified the system portion, the analysis determines what's ofthe system portion is to be evaluated. At a high level, the evaluationoptions are the evaluation perspectives of understanding (e g, knowledgeand/or intent of the system), implementation (e.g., how the system wasdeveloped), and operation (e.g., how the system fulfills itsobjectives).

For the understanding evaluation perspective, the analysis system canevaluate the understanding of the guidelines; the understanding of thesystem requirements; the understanding of the system design; theunderstanding of the system build; the understanding of the systemfunctions; the understanding of the security functions; and/or theunderstanding of the system assets.

For the implementation evaluation perspective, the analysis system canevaluate the development of the guidelines; the development of thesystem requirements; the development of the system design; thedevelopment of the system build; the development of the systemfunctions; the development of the security functions; and/or thedevelopment of the system assets.

For the operation evaluation perspective, the analysis system canevaluate the fulfillment of the guidelines by the system requirements;the fulfillment of the guidelines and/or the system requirements by thesystem design; the fulfillment of the guidelines, the systemrequirements, and/or the system design by the system build; the systemfunctions' fulfillment of the guidelines, the system requirements, thesystem design, and/or the system build; the security functions'fulfillment of the guidelines, the system requirements, the systemdesign, and/or the system build; and/or the system assets' fulfillmentof the guidelines, the system requirements, the system design, and/orthe system build.

The level of evaluation includes selecting one or more evaluationmetrics, selecting one or more evaluation modalities for each selectedevaluation metric, and selecting one or more evaluation outputs for theevaluation. The evaluation metrics include process, policy, procedure,documentation, automation, and/or certification. The evaluationmodalities include sufficiency, effectiveness, quantity of use,appropriate use, and/or consistency of use. The outputs includesevaluation ratings, identifying deficiencies, and/or auto-correctingdeficiencies.

As an example, the system portion is selected to be a particulardepartment. As such, all system assets associated with the particulardepartment are included in the system portion. Continuing with theexample, the understanding of the system requirements of the selectedsystem portion is to be evaluated. For this evaluation, all sixevaluation metrics will be used and all five evaluation modalities willbe used to produce an evaluation rating of understanding (e.g.,knowledge and/or intent) of the system requirements for the systemassets of the particular department. The resulting evaluation rating maybe a combination of a plurality of evaluations ratings, where anevaluation rating of the plurality of evaluation rating is for aspecific combination of an evaluation metric and an evaluation modality(e.g., sufficiency of processes, effectiveness of policies, etc.).

FIG. 75 is a schematic block diagram of an embodiment of an analysisunit 580 of an analysis system 10. The analysis unit 580, which may beone or more processing modules of one or more computing entities,receives a collection of data 581 regarding a system aspect and receivesdata analysis parameters 265. From the data analysis parameters 265, theanalysis unit 580 determines one or more evaluation perspectives, one ormore evaluation modalities, one or more evaluation metrics, one or moreevaluation viewpoints, and/or one or more evaluation categories.

The analysis unit 580 processes the collection of data 581 in accordancewith one or more evaluation perspectives, one or more evaluationmodalities, one or more evaluation metrics, one or more evaluationviewpoints, and/or one or more evaluation categories to produce one ormore evaluation outputs 582. The collection of data 581 is at least partof the pre-processed data 414 received by the data analysis module 252of FIG. 35 , which, for this embodiment, is at least part of theevaluation unit 580. The collection of data 581, the processing of theevaluation unit 580, the system aspect, the evaluation metrics, and anevaluation aspect will discussed in greater detail with reference to oneor more subsequent figures.

FIG. 76 is a diagram of an example of a system aspect, evaluation ratingmetrics, and an evaluation aspect of a system. FIG. 76 is similar toFIGS. 43 and 44 and is shown on the same sheet with FIG. 75 forconvenience. With respect to the analysis unit 580 and its operations,the system aspect includes one or more system elements, one or moresystem modes, and/or one or more system criteria; the evaluation metricsincludes one or more processes, one or more policies, one or moreprocedures, one or more documents, one or more certifications, and/orone or more automations; and the evaluation aspect includes one or moreevaluation perspectives, one or more evaluation viewpoints, one or moreevaluation categories (and/or sub-categories), and/or one or moreevaluation modalities.

FIG. 77 is a diagram of an example of a collection of data 581 that isorganized based on evaluation viewpoint. A first grouping of data isregarding disclosed data; a second grouping of data is regardingdiscovered data; and a third grouping is regarding desired data. Withineach evaluation viewpoint grouping, the data is further organized basedon evaluation categories of identify, protect, detect, respond, andrecover.

Each data group based on evaluation categories may be further organized.For example, as shown in FIG. 78 , each evaluation category data isfurther organized based on system element data, system mode data, systemcriteria data, system objectives data, and evaluation metric data. Thedata may further still further organized as shown in FIG. 79 .

In FIG. 79 , the evaluation metric data is organized by process, policy,document, automation, certification, and procedure. For example, eachprocess relating to an evaluation category of an evaluation viewpoint isan individual piece of data that can evaluated. The objectives data isfurther organized based on relevant objectives of the evaluationcategory of the evaluation viewpoint for the system aspect. Similarly,the system criteria data is further organized by guidelines, systemrequirements, system design, system build, and resulting system.

The system element data is further organized based on system functions,security functions, and/or system elements, which one or more assets(physical and/or conceptual). The system mode data intersects with partof the system element data with respect to assets, system functions, andsecurity functions.

By organizing the data into particular groups, the particular groups canbe individually evaluated to produce a specific evaluation rating, whichcan be combined with other evaluation ratings to produce an overallevaluation rating. For example, an evaluation is conducted on discloseddata regarding the evaluation category of protect for the selectedsystem portion. To perform the evaluation, the analysis system utilizesthe evaluation metric data pertaining to protection of the selectedsystem portion, the objective data pertaining to protection of theselected system portion, the system criteria data pertaining toprotection of the selected system portion, the system element datapertaining to protection of the selected system portion, and/or thesystem mode data pertaining to protection of the selected systemportion.

FIG. 80 is a diagram of an example of at least some data of a collectionof data for use by an analysis system to generate an evaluation ratingfor a system, or portion thereof. For the evaluation category ofidentify, the sub-categories and/or sub-sub categories are cues fordetermining what data to gather for an identify evaluation. Thesub-categories include asset management, business environment,governance, risk management, access control, awareness & training, anddata security.

The asset management sub-category includes the sub-sub categories of HWinventoried, SW inventoried, data flow mapped out, external systemscataloged, resources have been prioritized, and security roles have beenestablished. The business environment sub-category includes the sub-subcategories of supply chain roles defined, industry criticalinfrastructure identified, business priorities established, criticalservices identified, and resiliency requirements identified.

The governance sub-category includes the sub-sub categories of securitypolicies are established, security factors aligned, and legalrequirements are identified. The risk assessment sub-category includesthe sub-sub categories of vulnerabilities identified, external sourcesare leveraged, threats are identified, business impacts are identified,risk levels are identified, and risk responses are identified. The riskmanagement sub-category includes the sub-sub categories of riskmanagement processes are established, risk tolerances are established,and risk tolerances are tied to business environment.

The access control sub-category includes the sub-sub categories ofremote access control is defined, permissions are defined, and networkintegrity is defined. The awareness & training sub-category includes thesub-sub categories of users are trained, user privileges are known,third party responsibilities are known, executive responsibilities areknown, and IT and security responsibilities are known. The data securitysub-category includes the sub-sub categories of data at rest protocolsare established, data in transit protocols are established, formal assetmanagement protocols are established, adequate capacity of the system isestablished, data leak prevention protocols are established, integritychecking protocols are established, and use and development separationprotocols are established.

The sub-categories and sub-sub categories of other categories may alsobe used as cues for identifying data to be part of the collection ofdata. The various sub-categories and sub-sub categories of the othercategories are discussed with reference to FIGS. 46-49 .

FIG. 81 is a diagram of another example of at least some data acollection of data for use by an analysis system to generate anevaluation rating for a system, or portion thereof. In this example, thedata includes one or more of diagrams, one or more designspecifications, one or more purchases, one or more installation notes,one or more maintenance records, one or more user information records,one or more device information records, one or more operating manuals,and/or one or more other documents regarding a system aspect.

A diagram is a data flow diagram, an HLD diagram, an LLD diagram, a DLDdiagram, an operation flowchart, a software architecture diagram, ahardware architecture diagram, and/or other diagram regarding, thedesign, build, and/or operation of the system, or a portion thereof. Adesign specification is a security specification, a hardwarespecification, a software specification, a data flow specification, abusiness operation specification, a build specification, and/or otherspecification regarding the system, or a portion thereof.

A purchase is a purchase order, a purchase fulfillment document, bill ofladen, a quote, a receipt, and/or other information regarding purchasesof assets of the system, or a portion thereof. An installation note is arecord regarding the installation of an asset of the system, or portionthereof. A maintenance record is a record regarding each maintenanceservice performed on an asset of the system, or portion thereof.

User information includes affiliation of a user with one or more assetsof the system, or portion thereof. User information may also include alog of use of the one or more assets by the user or others. Userinformation may also include privileges and/or restrictions imposed onthe use of the one or more assets.

Device information includes an identity for an asset of the system, orportion thereof. A device is identified by vendor information (e.g.,name, address, contact person information, etc.), a serial number, adevice description, a device model number, a version, a generation, apurchase date, an installation date, a service date, and/or othermechanism for identifying a device.

FIG. 82 is a diagram of another example of at least some data of acollection of data for use by an analysis system to generate anevaluation rating for a system, or portion thereof. In particular, thisexample illustrates assets of the system, or portion thereof, that wouldbe part of the data and/or engaged with to obtain further information,which may become part of the collection of data.

As shown, asset information of the system, or portion thereof, includesa list of network devices (e.g., hardware and/or software), a list ofnetworking tools, a list of security devices (e.g., hardware and/orsoftware), a list of security tools, a list of storage devices (e.g.,hardware and/or software), a list of servers (e.g., hardware and/orsoftware), a list of user applications, a list of user devices (e.g.,hardware and/or software), a list of design tools, an list of systemapplications, and/or a list of verification tools. Recall that a tool isa program that functions to develop, repair, and/or enhance otherprograms and/or hardware of the system, or portion thereof.

Each list of devices includes vendor information (e.g., name, address,contact person information, etc.), a serial number, a devicedescription, a device model number, a version, a generation, a purchasedate, an installation date, a service date, and/or other mechanism foridentifying a device. Each list of software includes vendor information(e.g., name, address, contact person information, etc.), a serialnumber, a software description, a software model number, a version, ageneration, a purchase date, an installation date, a service date,and/or other mechanism for identifying software. Each list of toolsincludes vendor information (e.g., name, address, contact personinformation, etc.), a serial number, a tool description, a tool modelnumber, a version, a generation, a purchase date, an installation date,a service date, and/or other mechanism for identifying a tool.

FIG. 83 is a diagram of another example of at least some data of acollection of data for use by an analysis system to generate anevaluation rating for a system, or portion thereof. In particular, thisexample illustrates a list of user devices in a tabular form. The listincludes a plurality of columns for various pieces of informationregarding a user device and a plurality of rows; one row for each userdevice.

The columns include a user ID, a user level, a user role, hardware (HW)information, an IP address, user application software (SW) information,device application SW information, device use information, and/or devicemaintenance information. The user ID includes an individual identifierif a user and may further include an organization ID, a division ID, adepartment ID, a group ID, and/or a sub-group ID. The user level will bedescribed in greater detail with reference to FIG. 84 and the user rolewill be described in greater detail with reference to FIG. 85 .

The HW information field stores information regarding the hardware ofthe device. For example, the HW information includes informationregarding a computing device such as vendor information, a serialnumber, a description of the computing device, a computing device modelnumber, a version of the computing device, a generation of the computingdevice, and/or other mechanism for identifying a computing device. TheHW information may further store information regarding the components ofthe computing device such as the motherboard, the processor, videographics card, network card, connection ports, and/or memory.

The user application SW information field stores information regardingthe user applications installed on the user's computing device. Forexample, the user application SW information includes informationregarding a SW program (e.g., spreadsheet, word processing, database,email, etc.) such as vendor information, a serial number, a descriptionof the program, a program model number, a version of the program, ageneration of the program, and/or other mechanism for identifying aprogram. The device SW information includes similar information, but fordevice applications (e.g., operating system, drivers, security, etc.).

The device use data field stores data regarding the use of the device(e.g., use of the computing device and software running on it). Forexample, the device use data includes a log of use of a userapplication, or program (e.g., time of thy, duration of use, dateinformation, etc.). As another example, the device use data includes alog of data communications to and from the device. As yet anotherexample, the device use data includes a log of network accesses. As afurther example, the device use data includes a log of server access(e.g., local and/or remote servers). As still further example, thedevice use data includes a log of storage access (e.g., local and/orremote memory).

The maintenance field stores data regarding the maintenance of thedevice and/or its components. As an example, the maintenance dataincludes a purchase date, purchase information, an installation date,installation notes, a service date, services notes, and/or othermaintenance data of the device and/or its components.

FIG. 84 is a diagram of another example of user levels of the deviceinformation of FIG. 83 . In this illustration there are three userlevels (e.g., C-Level, director level, general level). In practice,there may be more or less user levels than three. For each user levelthere are options for data access privileges, data access restrictions,network access privileges, network access restrictions, server accessprivileges, server access restrictions, storage access privileges,storage access restrictions, required user applications, required deviceapplications, and/or prohibited user applications.

FIG. 85 is a diagram of another example of user roles of the deviceinformation of FIG. 83 . In this illustration there are four user roles(e.g., project manager, engineer, quality control, administration). Inpractice, there may be more or less user roles than four. For each userrole there are options for data access privileges, data accessrestrictions, network access privileges, network access restrictions,server access privileges, server access restrictions, storage accessprivileges, storage access restrictions, required user applications,required device applications, and/or prohibited user applications.

FIG. 86 is a diagram of another example of a collection of data 581 thatis organized based on evaluation viewpoint. A first grouping of data isregarding disclosed data; a second grouping of data is regardingdiscovered data; and a third grouping is regarding desired data. Withineach evaluation viewpoint grouping, the data is further organized basedon system criteria of guidelines, system requirements, design, build,and/or operation of the resulting system. The collection of data may befurther organized as shown in FIG. 87 . In FIG. 87 each system criteriais further organized by system element, system model, evaluationcategory, objectives, and/or evaluation metric.

FIG. 88 is a diagram of an example of a table for storing at least somedata of a collection of data. The table includes a plurality of columnsand a plurality of rows. The rows include a header row and a row foreach piece of data being stored. The columns include a name field, arecord number field, a system element ID field, a system criteria IDfield, a system mode ID field, an evaluation viewpoint ID field, anevaluation category ID field (which could include sub-categoryidentifiers and/or sub-sub category identifies), an evaluation metric IDfield, and a data field.

Each of the record number field, the system element ID field, the systemcriteria ID field, the system mode ID field, the evaluation viewpoint IDfield, the evaluation category ID field, and the evaluation metric IDfield may use a coding scheme to specifically identify the appropriatedata for the field. As an example, a system element includes one or moresystem assets which include one or more physical and conceptual assets(e.g., a physical asset (code 00) or a conceptual asset (code 01)).Thus, the system element field for each piece of data would indicate aphysical asset or a conceptual asset. As another example, the systemcriteria field could use the following code structure:

-   -   0000 for guidelines;    -   0001 for system requirements;    -   0010 for system design;    -   0011 for system build;    -   0100 for the resulting system;    -   1111 for all of the system criteria;    -   0101 for a 1^(st) combination (e.g., design and build); and so        on.

With such an organizational structure, data can be retrieved in avariety of ways to support a variety of evaluation analysis. Forexample, an evaluation regarding the processes to develop guidelines,data having a system criteria code of 0000 and an evaluation metric codeof 0000 can be readily retrieved and evaluated.

FIG. 89 is a schematic block diagram of another embodiment of ananalysis unit 580 that includes the data analysis module 252 and theevaluation processing module 254 of FIG. 35 . The data analysis module252 includes a data module 321 and an analyze & score module 336.

In an example, the data module 321 outputs source data 337 of thecollection of data 581 in accordance with the data analysis parameters.An example of this was discussed with reference to FIG. 41 . The analyze& score module 336 generates one or more evaluation ratings 219 based onthe source data 337 and in accordance with the data analysis parameters265. Further examples of this will be discussed with reference to one ormore of the subsequent figures.

The evaluation processing module 254 processes the rating(s) 219 inaccordance with the data analysis parameters 265 to produce deficiencies232 and/or auto-corrections 235. An example of this was discussed withreference to FIG. 35 .

FIG. 90 is a schematic block diagram of an embodiment of an analyze &score module 336 that includes a process rating module 601, a policyrating module 602, a procedure rating module 603, a certification ratingmodule 604, a documentation rating module 605, an automation ratingmodule 606, and a cumulative rating module 607. In general, the analyze& score module generates an evaluation rating 219 from a collection ofdata 581 based on data analysis parameters 265.

The process rating module 601 evaluates the collection of data 581, orportion thereof, (e.g., at least part of the pre-processed data of FIG.35 ) to produce a process evaluation rating in accordance with processanalysis parameters of the data analysis parameters 265. The processanalysis parameters indicate how the collection of data is to beevaluated with respect to processes of the system, or portion thereof.As an example, the process analysis parameters include:

-   -   an instruction to compare processes of the data 581 with a list        of processes the system, or portion thereof, should have;    -   an instruction to count the number of processes of data 581 and        compare it with a quantity of processes the system, or portion        thereof, should have;    -   an instruction to determine last revisions of processes of data        581 and/or to determine an age of last revisions;    -   an instruction to determine frequency of use of processes of        data 581;    -   an instruction to determine a volume of access of processes of        data 581;    -   an instruction to evaluate a process of data 581 with respect to        a checklist regarding content of the process (e.g., what should        be in the process);    -   a scaling factor based on the size of the system, or portion        thereof;    -   a scaling factor based on the size of the organization;    -   an instruction to compare a balance of local processes with        respect to system-wide processes;    -   an instruction to compare topics of the processes of data 581        with desired topics for processes (which may be at least        partially derived from the evaluation category and/or        sub-categories); and/or    -   an instruction to evaluate language use within processes of data        581.

The process rating module 601 can rate the data 581 at three or morelevels. The first level is that the system has processes, the system hasthe right number of processes, and/or the system has processes thataddress the right topics. The second level digs into the processesthemselves to determine whether they are adequately covering therequirements of the system. The third level evaluates how well theprocesses are used and how well they are adhered to.

As an example, the process rating module 601 generates a processevaluation rating based on a comparison of the processes of the data 581with a list of processes the system, or portion thereof, should have. Ifall of the processes on the list are found in the data 581, then theprocess evaluation rating is high. The fewer processes on the list thatfound in the data 581, the lower the process evaluation rating will be.

As another example, the process rating module 601 generates a processevaluation rating based on a determination of the last revisions ofprocesses of data 581 and/or to determine an age of last revisions. As aspecific example, if processes are revised at a rate that corresponds toa rate of revision in the industry, then a relatively high processevaluation rate would be produced. As another specific example, ifprocesses are revised at a much lower rate that corresponds to a rate ofrevision in the industry, then a relatively low process evaluation ratewould be produced (implies a lack of attention to the processes). As yetanother specific example, if processes are revised at a much higher ratethat corresponds to a rate of revision in the industry, then arelatively low process evaluation rate would be produced (impliesprocesses are inaccurate, incomplete, and/or created with a lack ofknowledge as to what's needed).

As another example, the process rating module 601 generates a processevaluation rating based on a determination of frequency of use ofprocesses of data 581. As a specific example, if processes are used at afrequency (e.g., x times per week) that corresponds to a frequency ofuse in the industry, then a relatively high process evaluation ratewould be produced. As another specific example, if processes are used ata much lower frequency that corresponds to a frequency of use in theindustry, then a relatively low process evaluation rate would beproduced (implies a lack of using and adhering to the processes). As yetanother specific example, if processes are used at a much higherfrequency that corresponds to a frequency of use in the industry, then arelatively low process evaluation rate would be produced (impliesprocesses are inaccuracy, incompleteness, and/or difficult to use).

As another example, the process rating module 601 generates a processevaluation rating based on an evaluation of a process of data 581 withrespect to a checklist regarding content of the policy (e.g., whatshould be in the policy, which may be based, at least in part, on anevaluation category, sub-category, and/or sub-sub category). As aspecific example, the topics contained in the process of data 581 iscompared to a checklist of desired topics for such a process. If all ofthe topics on the checklist are found in the process of data 581, thenthe process evaluation rating is high. The fewer topics on the checklistthat found in the process of data 581, the lower the process evaluationrating will be.

As another example, the process rating module 601 generates a processevaluation rating based on a comparison of balance between localprocesses of data 581 and system-wide processes of data 581. As aspecific example, most security processes should be system-wide. Thus,if there are a certain percentage (e.g., less than 10%) of securityprocesses that are local, then a relatively high process evaluationrating will be generated. Conversely, the greater the percentage oflocal security processes, the lower the process evaluation rating willbe.

As another example, the process rating module 601 generates a processevaluation rating based on evaluation of language use within processesof data 581. As a specific example, most security requirements aremandatory Thus, if the policy includes too much use of the word “may”(which implies optionality) versus the word “shall (which implies must),the lower the process evaluation rating will be.

The process rating module 601 may perform a plurality of the aboveexamples of process evaluation to produce a plurality of processevaluation ratings. The process rating module 601 may output theplurality of the process evaluation ratings to the cumulative ratingmodule 607. Alternatively, the process rating module 601 may perform afunction (e.g., a weight average, standard deviation, statisticalanalysis, etc.) on the plurality of process evaluation ratings toproduce a process evaluation rating that's provided to the cumulativerating module 607.

The policy rating module 602 evaluates the collection of data 581, orportion thereof, (e.g., pre-processed data of FIG. 35 ) to produce apolicy evaluation rating in accordance with policy analysis parametersof the data analysis parameters 265. The policy analysis parametersindicate how the collection of data is to be evaluated with respect topolicies of the system, or portion thereof. As an example, the policyanalysis parameters include:

-   -   an instruction to compare policies of the data 581 with a list        of policies the system, or portion thereof, should have;    -   an instruction to count the number of policies of data 581 and        compare it with a quantity of policies the system, or portion        thereof, should have;    -   an instruction to determine last revisions of policies of data        581 and/or to determine an age of last revisions;    -   an instruction to determine frequency of use of policies of data        581;    -   an instruction to determine a volume of access of policies of        data 581;    -   an instruction to evaluate a policy of data 581 with respect to        a checklist regarding content of the policy (e.g., what should        be in the policy);    -   a scaling factor based on the size of the system, or portion        thereof;    -   a scaling factor based on the size of the organization;    -   an instruction to compare a balance of local policies with        respect to system-wide policies;    -   an instruction to compare topics of the policies of data 581        with desired topics for policies (which may be at least        partially derived from the evaluation category and/or        sub-categories); and/or    -   an instruction to evaluate language use within policies of data        581.

The policy rating module 602 can rate the data 581 at three or morelevels. The first level is that the system has policies, the system hasthe right number of policies, and/or the system has policies thataddress the right topics. The second level digs into the policiesthemselves to determine whether they are adequately covering therequirements of the system. The third level evaluates how well thepolicies are used and how well they are adhered to.

The procedure rating module 603 evaluates the collection of data 581, orportion thereof, (e.g., pre-processed data of FIG. 35 ) to produce aprocedure evaluation rating in accordance with procedure analysisparameters of the data analysis parameters 265. The procedure analysisparameters indicate how the collection of data is to be evaluated withrespect to procedures of the system, or portion thereof. As an example,the procedure analysis parameters include:

-   -   an instruction to compare procedures of the data 581 with a list        of procedures the system, or portion thereof, should have;    -   an instruction to count the number of procedures of data 581 and        compare it with a quantity of procedures the system, or portion        thereof, should have;    -   an instruction to determine last revisions of procedures of data        581 and/or to determine an age of last revisions;    -   an instruction to determine frequency of use of procedures of        data 581;    -   an instruction to determine a volume of access of procedures of        data 581;    -   an instruction to evaluate a procedure of data 581 with respect        to a checklist regarding content of the procedure (e.g., what        should be in the procedure);    -   a scaling factor based on the size of the system, or portion        thereof;    -   a scaling factor based on the size of the organization;    -   an instruction to compare a balance of local procedures with        respect to system-wide procedures;    -   an instruction to compare topics of the procedures of data 581        with desired topics for procedures (which may be at least        partially derived from the evaluation category and/or        sub-categories); and/or    -   an instruction to evaluate language use within procedures of        data 581.

The procedure rating module 603 can rate the data 581 at three or morelevels. The first level is that the system has procedures, the systemhas the right number of procedures, and/or the system has proceduresthat address the right topics. The second level digs into the proceduresthemselves to determine whether they are adequately covering therequirements of the system. The third level evaluates how well theprocedures are used and how well they are adhered to.

The certification rating module 604 evaluates the collection of data581, or portion thereof, (e.g., pre-processed data of FIG. 35 ) toproduce a certification evaluation rating in accordance withcertification analysis parameters of the data analysis parameters 265.The certification analysis parameters indicate how the collection ofdata is to be evaluated with respect to certifications of the system, orportion thereof. As an example, the certification analysis parametersinclude:

-   -   an instruction to compare certifications of the data 581 with a        list of certifications the system, or portion thereof, should        have;    -   an instruction to count the number of certifications of data 581        and compare it with a quantity of certifications the system, or        portion thereof, should have;    -   an instruction to determine last revisions of certifications of        data 581 and/or to determine an age of last revisions;    -   an instruction to evaluate a certification of data 581 with        respect to a checklist regarding content of the certification        (e.g., what should be certified and/or how it should be        certified);    -   a scaling factor based on the size of the system, or portion        thereof;    -   a scaling factor based on the size of the organization; and    -   an instruction to compare a balance of local certifications with        respect to system-wide certifications.

The certification rating module 603 can rate the data 581 at three ormore levels. The first level is that the system has certifications, thesystem has the right number of certifications, and/or the system hascertifications that address the right topics. The second level digs intothe certifications themselves to determine whether they are adequatelycovering the requirements of the system. The third level evaluates howwell the certifications are maintained and updated.

The documentation rating module 603 evaluates the collection of data581, or portion thereof, (e.g., pre-processed data of FIG. 35 ) toproduce a documentation evaluation rating in accordance withdocumentation analysis parameters of the data analysis parameters 265.The documentation analysis parameters indicate how the collection ofdata is to be evaluated with respect to documentation of the system, orportion thereof. As an example, the documentation analysis parametersinclude:

-   -   an instruction to compare documentation of the data 581 with a        list of documentation the system, or portion thereof, should        have;    -   an instruction to count the number of documentation of data 581        and compare it with a quantity of documentation the system, or        portion thereof, should have;    -   an instruction to determine last revisions of documentation of        data 581 and/or to determine an age of last revisions;    -   an instruction to determine frequency of use and/or creation of        documentation of data 581;    -   an instruction to determine a volume of access of documentation        of data 581;    -   an instruction to evaluate a document of data 581 with respect        to a checklist regarding content of the document (e.g., what        should be in the document);    -   a scaling factor based on the size of the system, or portion        thereof;    -   a scaling factor based on the size of the organization;    -   an instruction to compare a balance of local documents with        respect to system-wide documents;    -   an instruction to compare topics of the documentation of data        581 with desired topics for documentation (which may be at least        partially derived from the evaluation category and/or        sub-categories); and/or    -   an instruction to evaluate language use within documentation of        data 581.

The documentation rating module 605 can rate the data 581 at three ormore levels. The first level is that the system has documentation, thesystem has the right number of documents, and/or the system hasdocuments that address the right topics. The second level digs into thedocuments themselves to determine whether they are adequately coveringthe requirements of the system. The third level evaluates how well thedocumentation is used and how well it is maintained.

The automation rating module 606 evaluates the collection of data 581,or portion thereof, (e.g., pre-processed data of FIG. 35 ) to produce anautomation evaluation rating in accordance with automation analysisparameters of the data analysis parameters 265. The automation analysisparameters indicate how the collection of data is to be evaluated withrespect to automation of the system, or portion thereof. As an example,the automation analysis parameters include:

-   -   an instruction to compare automation of the data 581 with a list        of automation the system, or portion thereof, should have;    -   an instruction to count the number of automation of data 581 and        compare it with a quantity of automation the system, or portion        thereof, should have;    -   an instruction to determine last revisions of automation of data        581 and/or to determine an age of last revisions;    -   an instruction to determine frequency of use of automation of        data 581;    -   an instruction to determine a volume of access of automation of        data 581;    -   an instruction to evaluate an automation of data 581 with        respect to a checklist regarding content of the automation        (e.g., what the automation should do);    -   a scaling factor based on the size of the system, or portion        thereof;    -   a scaling factor based on the size of the organization;    -   an instruction to compare a balance of local automation with        respect to system-wide automation;    -   an instruction to compare topics of the automation of data 581        with desired topics for automation (which may be at least        partially derived from the evaluation category and/or        sub-categories); and/or    -   an instruction to evaluate operation use of automation of data        581.

The automation rating module 606 can rate the data 581 at three or morelevels. The first level is that the system has automation, the systemhas the right number of automation, and/or the system has automationthat address the right topics. The second level digs into the automationthemselves to determine whether they are adequately covering therequirements of the system. The third level evaluates how well theautomations are used and how well they are adhered to.

The cumulative rating module 607 receives one or more process evaluationratings, one or more policy evaluation ratings, one or more procedureevaluation ratings, one or more certification evaluation ratings, one ormore documentation evaluation ratings, and/or one or more automationevaluation ratings. The cumulative rating module 607 may output theevaluation ratings it receives as the identification rating 608.Alternatively, the cumulative rating module 607 performs a function(e.g., a weight average, standard deviation, statistical analysis, etc.)on the evaluation ratings it receives to produce the identificationrating 608.

FIG. 91 is a schematic block diagram of another embodiment of an analyze& score module 336 that is similar to the data analysis module of FIG.90 . In this embodiment, the analyze & score module 336 includes a dataparsing module 609, which parses the data 581 into process data, policydata, procedure data, certification data, documentation data, and/orautomation data prior to processing by the respective modules 601-606.

FIG. 92 is a schematic block diagram of an embodiment of a rating module595, which is representative of the structure and general functioning ofthe process rating module 601, the policy rating module 602, theprocedure rating module 603, the certification rating module 604, thedocumentation rating module 605, and/or the automation rating module606. The rating module 595 includes a sufficiency module 610, aneffectiveness module 611, a quantity of use module 612, an appropriateuse module 613, a consistency of use module 614, a switch matrix 615, anunderstanding module 616, an implementation module 617, an operationmodule 618, and a self-analysis module 619.

In an example, the sufficiency module 610 receives at least some of thecollection of data 581 to produce a quantity of evaluation metric 620.For example, when the rating module 595 is the process rating module601, the sufficiency module 610 evaluates the quantity of processes ofthe data 581 with respect to the particular evaluation as indicated perthe data analysis parameters 265 (e.g., processes with respect tocreating system requirements; processes regarding security functions fora group; etc.). In a more specific example, the sufficiency module 610counts the number of relevant processes of the data 581 and compares thecount to an expected number of relevant processes to generate thequantity of evaluation metric 620 for the processes. As another specificexample, the sufficiency module 610 compares the relevant processes ofthe data 581 with a checklist of expected processes to generate thequantity of evaluation metric 620 for the processes.

When the rating module 595 is the policy rating module 602, thesufficiency module 610 evaluates the quantity of policies of the data581 with respect to the particular evaluation as indicated per the dataanalysis parameters 265 (e.g., policies with respect to creating systemrequirements; policies regarding security functions for a group; etc.).In a more specific example, the sufficiency module 610 counts the numberof relevant policies of the data 581 and compares the count to anexpected number of relevant policies to generate the quantity ofevaluation metric 620 for the policies. As another specific example, thesufficiency module 610 compares the relevant policies of the data 581with a checklist of expected policies to generate the quantity ofevaluation metric 620 for the policies.

When the rating module 595 is the procedure rating module 603, thesufficiency module 610 evaluates the quantity of procedures of the data581 with respect to the particular evaluation as indicated per the dataanalysis parameters 265 (e.g., procedures with respect to creatingsystem requirements; procedures regarding security functions for agroup; etc.). In a more specific example, the sufficiency module 610counts the number of relevant procedures of the data 581 and comparesthe count to an expected number of relevant procedures to generate thequantity of evaluation metric 620 for the procedures. As anotherspecific example, the sufficiency module 610 compares the relevantprocedures of the data 581 with a checklist of expected procedures togenerate the quantity of evaluation metric 620 for the procedures.

When the rating module 595 is the certification rating module 604, thesufficiency module 610 evaluates the quantity of certificates of thedata 581 with respect to the particular evaluation as indicated per thedata analysis parameters 265 (e.g., certificates with respect tocreating system requirements; certificates regarding security functionsfor a group; etc.). In a more specific example, the sufficiency module610 counts the number of relevant certificates of the data 581 andcompares the count to an expected number of relevant certificates togenerate the quantity of evaluation metric 620 for the certificates. Asanother specific example, the sufficiency module 610 compares therelevant certificates of the data 581 with a checklist of expectedcertificates to generate the quantity of evaluation metric 620 for thecertificates.

When the rating module 595 is the documentation rating module 605, thesufficiency module 610 evaluates the quantity of documents of the data581 with respect to the particular evaluation as indicated per the dataanalysis parameters 265 (e.g., documents with respect to creating systemrequirements; documents regarding security functions for a group; etc.).In a more specific example, the sufficiency module 610 counts the numberof relevant documents of the data 581 and compares the count to anexpected number of relevant documents to generate the quantity ofevaluation metric 620 for the documents. As another specific example,the sufficiency module 610 compares the relevant documents of the data581 with a checklist of expected documents to generate the quantity ofevaluation metric 620 for the documents.

When the rating module 595 is the automation rating module 606, thesufficiency module 610 evaluates the quantity of automations of the data581 with respect to the particular evaluation as indicated per the dataanalysis parameters 265 (e.g., automations with respect to creatingsystem requirements; automations regarding security functions for agroup; etc.). In a more specific example, the sufficiency module 610counts the number of relevant automations of the data 581 and comparesthe count to an expected number of relevant automations to generate thequantity of evaluation metric 620 for the automations. As anotherspecific example, the sufficiency module 610 compares the relevantautomations of the data 581 with a checklist of expected automations togenerate the quantity of evaluation metric 620 for the automations.

Within the rating module 595, the effectiveness module 611 receives atleast some of the collection of data 581 to produce a quantifiedeffectiveness of evaluation metric 622. For example, when the ratingmodule 595 is the process rating module 601, the effectiveness module611 evaluates the effectiveness of processes of the data 581 withrespect to the particular evaluation as indicated per the data analysisparameters 265 (e.g., processes with respect to creating systemrequirements; processes regarding security functions for a group; etc.).In a more specific example, the effectiveness module 611 compares thecontent of relevant processes of the data 581 with an expected contentof processes to generate the quantified effectiveness of evaluationmetric 622 for the processes.

When the rating module 595 is the policy rating module 602, theeffectiveness module 611 evaluates the effectiveness of policies of thedata 581 with respect to the particular evaluation as indicated per thedata analysis parameters 265 (e.g., policies with respect to creatingsystem requirements; policies regarding security functions for a group;etc.). In a more specific example, the effectiveness module 611 comparesthe content of relevant policies of the data 581 with an expectedcontent of polices to generate the quantified effectiveness ofevaluation metric 622 for the policies.

When the rating module 595 is the procedure rating module 603, theeffectiveness module 611 evaluates the effectiveness of procedures ofthe data 581 with respect to the particular evaluation as indicated perthe data analysis parameters 265 (e.g., procedures with respect tocreating system requirements; procedures regarding security functionsfora group; etc.). In a more specific example, the effectiveness module611 compares the content of relevant procedures of the data 581 with anexpected content of procedures to generate the quantified effectivenessof evaluation metric 622 for the procedures.

When the rating module 595 is the certification rating module 604, theeffectiveness module 611 evaluates the effectiveness of certificates ofthe data 581 with respect to the particular evaluation as indicated perthe data analysis parameters 265 (e.g., certificates with respect tocreating system requirements; certificates regarding security functionsfor a group; etc.). In a more specific example, the effectiveness module611 compares the content of relevant certificates of the data 581 withan expected content of certificates to generate the quantifiedeffectiveness of evaluation metric 622 for the certificates.

When the rating module 595 is the documentation rating module 605, theeffectiveness module 611 evaluates the effectiveness of documents of thedata 581 with respect to the particular evaluation as indicated per thedata analysis parameters 265 (e.g., documents with respect to creatingsystem requirements; documents regarding security functions for a group;etc.). In a more specific example, the effectiveness module 611 comparesthe content of relevant documents of the data 581 with an expectedcontent of documents to generate the quantified effectiveness ofevaluation metric 622 for the documents.

When the rating module 595 is the automation rating module 606, theeffectiveness module 611 evaluates the effectiveness of automations ofthe data 581 with respect to the particular evaluation as indicated perthe data analysis parameters 265 (e.g., automation with respect tocreating system requirements; automation regarding security functionsfor a group; etc.). In a more specific example, the effectiveness module611 compares the content of relevant automation of the data 581 with anexpected content of automation to generate the quantified effectivenessof evaluation metric 622 for the automation.

Within the rating module 595, the quantity of use module 612 receives atleast some of the collection of data 581 to produce a quantity ofevaluation metric use 623. For example, when the rating module 595 isthe process rating module 601, the quantity of use module 612 evaluatesthe quantity of use of processes of the data 581 with respect to theparticular evaluation as indicated per the data analysis parameters 265(e.g., use of processes with respect to creating system requirements;use of processes regarding security functions for a group; etc.). In amore specific example, the quantity of use module 612 compares a countof use of relevant processes of the data 581 with an expected number ofuse of processes to generate the quantity of evaluation metric use 623for the processes.

When the rating module 595 is the policy rating module 602, the quantityof use module 612 evaluates the quantity of use of policies of the data581 with respect to the particular evaluation as indicated per the dataanalysis parameters 265 (e.g., use of policies with respect to creatingsystem requirements; use of policies regarding security functions for agroup; etc.). In a more specific example, the quantity of use module 612compares a count of use of relevant policies of the data 581 with anexpected number of use of policies to generate the quantity ofevaluation metric use 623 for the policies.

When the rating module 595 is the procedure rating module 603, thequantity of use module 612 evaluates the quantity of use of proceduresof the data 581 with respect to the particular evaluation as indicatedper the data analysis parameters 265 (e.g., use of procedures withrespect to creating system requirements; use of procedures regardingsecurity functions for a group; etc.). In a more specific example, thequantity of use module 612 compares a count of use of relevantprocedures of the data 581 with an expected number of use of proceduresto generate the quantity of evaluation metric use 623 for theprocedures.

When the rating module 595 is the certification rating module 604, thequantity of use module 612 evaluates the quantity of use of certificatesof the data 581 with respect to the particular evaluation as indicatedper the data analysis parameters 265 (e.g., use of certificates withrespect to creating system requirements; use of certificates regardingsecurity functions for a group; etc.). In a more specific example, thequantity of use module 612 compares a count of use of relevantcertificates of the data 581 with an expected number of use ofcertificates to generate the quantity of evaluation metric use 623 forthe certificates.

When the rating module 595 is the documentation rating module 605, thequantity of use module 612 evaluates the quantity of use of documents ofthe data 581 with respect to the particular evaluation as indicated perthe data analysis parameters 265 (e.g., use of documents with respect tocreating system requirements; use of documents regarding securityfunctions for a group; etc.). In a more specific example, the quantityof use module 612 compares a count of use of relevant documents of thedata 581 with an expected number of use of documents to generate thequantity of evaluation metric use 623 for the documentation.

When the rating module 595 is the automation rating module 606, thequantity of use module 612 evaluates the quantity of use of automationof the data 581 with respect to the particular evaluation as indicatedper the data analysis parameters 265 (e.g., use of automation withrespect to creating system requirements; use of automation regardingsecurity functions for a group; etc.). In a more specific example, thequantity of use module 612 compares a count of use of relevantautomation of the data 581 with an expected number of use of automationto generate the quantity of evaluation metric use 623 for theautomation.

Within the rating module 595, the appropriate use module 613 receives atleast some of the collection of data 581 to produce a quantifiedappropriate use of evaluation metric 624. For example, when the ratingmodule 595 is the process rating module 601, the appropriate use module613 evaluates the conditions of use of processes of the data 581 withrespect to the particular evaluation as indicated per the data analysisparameters 265 (e.g., conditions of use of processes with respect tocreating system requirements; conditions use of processes regardingsecurity functions for a group; etc.). In a more specific example, theappropriate use module 613 compares the conditions of use of relevantprocesses of the data 581 with an expected conditions of use ofprocesses to generate the quantified appropriate use of evaluationmetric 624 for the processes.

When the rating module 595 is the policy rating module 602, theappropriate use module 613 evaluates the conditions of use of policiesof the data 581 with respect to the particular evaluation as indicatedper the data analysis parameters 265 (e.g., conditions of use ofpolicies with respect to creating system requirements; conditions use ofpolicies regarding security functions for a group; etc.). In a morespecific example, the appropriate use module 613 compares the conditionsof use of relevant policies of the data 581 with an expected conditionsof use of policies to generate the quantified appropriate use ofevaluation metric 624 for the policies.

When the rating module 595 is the procedure rating module 603, theappropriate use module 613 evaluates the conditions of use of proceduresof the data 581 with respect to the particular evaluation as indicatedper the data analysis parameters 265 (e.g., conditions of use ofprocedures with respect to creating system requirements; conditions useof procedures regarding security functions for a group; etc.). In a morespecific example, the appropriate use module 613 compares the conditionsof use of relevant procedures of the data 581 with an expectedconditions of use of procedures to generate the quantified appropriateuse of evaluation metric 624 for the procedures.

When the rating module 595 is the certification rating module 604, theappropriate use module 613 evaluates the conditions of use ofcertificates of the data 581 with respect to the particular evaluationas indicated per the data analysis parameters 265 (e.g., conditions ofuse of certificates with respect to creating system requirements;conditions use of certificates regarding security functions for a group;etc.). In a more specific example, the appropriate use module 613compares the conditions of use of relevant certificates of the data 581with an expected conditions of use of certificates to generate thequantified appropriate use of evaluation metric 624 for thecertificates.

When the rating module 595 is the documentation rating module 605, theappropriate use module 613 evaluates the conditions of use of documentsof the data 581 with respect to the particular evaluation as indicatedper the data analysis parameters 265 (e.g., conditions of use ofdocuments with respect to creating system requirements; conditions useof documents regarding security functions for a group; etc.). In a morespecific example, the appropriate use module 613 compares the conditionsof use of relevant documents of the data 581 with an expected conditionsof use of documents to generate the quantified appropriate use ofevaluation metric 624 for the certificates.

When the rating module 595 is the automation rating module 606, theappropriate use module 613 evaluates the conditions of use of automationof the data 581 with respect to the particular evaluation as indicatedper the data analysis parameters 265 (e.g., conditions of use ofautomation with respect to creating system requirements; conditions useof automation regarding security functions for a group; etc.). In a morespecific example, the appropriate use module 613 compares the conditionsof use of relevant automation of the data 581 with an expectedconditions of use of automation to generate the quantified appropriateuse of evaluation metric 624 for the automation.

Within the rating module 595, the consistency of use module 614 receivesat least some of the collection of data 581 to produce a quantifiedconsistency of use of evaluation metric 625. For example, when therating module 595 is the process rating module 601, the consistency ofuse module 614 evaluates the situations of use of processes of the data581 with respect to the particular evaluation as indicated per the dataanalysis parameters 265 (e.g., situations of use of processes withrespect to creating system requirements; situations use of processesregarding security functions for a group; etc.). In a more specificexample, the consistency of use module 614 compares the situations ofuse of relevant processes of the data 581 with an expected situations ofuse of processes to generate the quantified consistency of use ofevaluation metric 625 for the processes.

When the rating module 595 is the policy rating module 602, theconsistency of use module 614 evaluates the situations of use ofpolicies of the data 581 with respect to the particular evaluation asindicated per the data analysis parameters 265 (e.g., situations of useof policies with respect to creating system requirements; situations useof policies regarding security functions for a group; etc.). In a morespecific example, the consistency of use module 614 compares thesituations of use of relevant policies of the data 581 with an expectedsituations of use of policies to generate the quantified consistency ofuse of evaluation metric 625 for the polices.

When the rating module 595 is the procedure rating module 603, theconsistency of use module 614 evaluates the situations of use ofprocedures of the data 581 with respect to the particular evaluation asindicated per the data analysis parameters 265 (e.g., situations of useof procedures with respect to creating system requirements; situationsuse of procedures regarding security functions for a group; etc.). In amore specific example, the consistency of use module 614 compares thesituations of use of relevant procedures of the data 581 with anexpected situations of use of procedures to generate the quantifiedconsistency use of evaluation metric 625 for the procedures.

When the rating module 595 is the certification rating module 604, theconsistency of use module 614 evaluates the situations of use ofcertificates of the data 581 with respect to the particular evaluationas indicated per the data analysis parameters 265 (e.g., situations ofuse of certificates with respect to creating system requirements;situations use of certificates regarding security functions for a group;etc.). In a more specific example, the consistency of use module 614compares the situations of use of relevant certificates of the data 581with an expected situations of use of certificates to generate thequantified consistency of use of evaluation metric 625 for thecertificates.

When the rating module 595 is the documentation rating module 605, theconsistency of use module 614 evaluates the situations of use ofdocuments of the data 581 with respect to the particular evaluation asindicated per the data analysis parameters 265 (e.g., situations of useof documents with respect to creating system requirements; situationsuse of documents regarding security functions for a group; etc.). In amore specific example, the consistency of use module 614 compares thesituations of use of relevant documents of the data 581 with an expectedsituations of use of documents to generate the quantified appropriateuse of evaluation metric 625 for the documents.

When the rating module 595 is the automation rating module 606, theconsistency of use module 614 evaluates the situations of use ofautomation of the data 581 with respect to the particular evaluation asindicated per the data analysis parameters 265 (e.g., situations of useof automation with respect to creating system requirements; situationsuse of automation regarding security functions for a group; etc.). In amore specific example, the consistency of use module 614 compares thesituations of use of relevant automation of the data 581 with anexpected situations of use of automation to generate the quantifiedappropriate use of evaluation metric 625 for the automation.

The understanding module 616 receives the quantity of evaluation metric620, the quantified effectiveness of evaluation metric 622, the quantityof evaluation metric use 623, the quantified appropriate use ofevaluation metric 624, and/or the quantified consistency of use ofevaluation metric 625 via the switch matrix 615 as indicated by aselection signal 621. The understanding module 616 processes thereceived input in accordance with an understanding reference 626 toproduce an understanding evaluation metric rating 627.

The implementation module 617 receives the quantity of evaluation metric620, the quantified effectiveness of evaluation metric 622, the quantityof evaluation metric use 623, the quantified appropriate use ofevaluation metric 624, and/or the quantified consistency of use ofevaluation metric 625 via the switch matrix 615 as indicated by aselection signal 621. The implementation module 617 processes thereceived input in accordance with an implementation reference 628 toproduce an implementation evaluation metric rating 629.

The operation module 618 receives the quantity of evaluation metric 620,the quantified effectiveness of evaluation metric 622, the quantity ofevaluation metric use 623, the quantified appropriate use of evaluationmetric 624, and/or the quantified consistency of use of evaluationmetric 625 via the switch matrix 615 as indicated by a selection signal621. The operation module 618 processes the received input in accordancewith an operation reference 630 to produce system evaluation metricrating 629 regarding assets, system functions, and/or securityfunctions.

The self-analysis module 619 receives the quantity of evaluation metric620, the quantified effectiveness of evaluation metric 622, the quantityof evaluation metric use 623, the quantified appropriate use ofevaluation metric 624, and/or the quantified consistency of use ofevaluation metric 625 via the switch matrix 615 as indicated by aselection signal 621. The self-analysis module 619 processes thereceived input in accordance with a self-analysis reference 632 toproduce a self-analysis evaluation metric rating 633.

FIG. 93 is a diagram of an example an evaluation matrix that includesevaluation perspectives and evaluation modalities. The evaluationperspectives includes understanding, implementation, and operation.Understanding is regarding the knowledge of the system, or portionthereof. For example, an understanding evaluation rating is reflectiveof how well the system is understood with respect to system objectives,how well the system objectives are understood, how good are the systemobjectives, and/or how well should the system be understood with respectto the system objectives.

The system objectives are regarding the various things the system issupposed to do. For example, system objectives include, but are notlimited to, business operations (e.g., corporate, finance, engineering,manufacturing, sales, marketing, etc.), data storage, data uses, datatransmission, data security, data control, data sharing, authorized use,system speed, system hardware architecture, system softwarearchitecture, maintenance requirements, expansion protocols, etc.

Implementation is regarding the accuracy, thoroughness, and/or structureof the development of the system, or portion thereof. For example, animplementation evaluation rating is reflective of how good are theguidelines, system requirements, system design, system build, and/orresulting system for fulfilling the system objectives. As anotherexample, an implementation evaluation rating is reflective of well thesystem requirements were developed from the guidelines. As anotherexample, an implementation evaluation rating is reflective of well thesystem design was developed from the guidelines and/or the systemrequirements. As another example, an implementation evaluation rating isreflective of well the system build was developed from the guidelines,the system requirements, and/or the system design. As another example,an implementation evaluation rating is reflective of well the resultingsystem was developed from the guidelines, the system requirements,system design, and/or the system build.

The evaluation modalities includes sufficiency, effectiveness, quantityof use, appropriate use, and consistency of use. The sufficiencymodality is regarding a count and/or checklist of data regarding eachevaluation metric that is found (e.g., is part of the disclosed and/ordiscovered data) and/or that the system should include (e.g., is part ofthe desired data). The evaluation metrics include processes, policies,procedures, documents, certifications, automations, and/or one or moreother measures regarding efficiency, completeness, reliability,capacity, accuracy, execution speed, bandwidth, and/or othercharacteristic of the system or portion thereof.

The effectiveness modality is regarding content review of the data forone or more of the evaluation metrics. The quantity of use modality isregarding a count of the use of the data for one or more of theevaluation metrics. The appropriate use modality is regarding conditionsin which the data for one or more of the evaluation metrics was used(e.g., relied on, created, edited, interpreted, etc.). The consistencyof use modality is regarding situations in which the data for one ormore of the evaluation metrics was used.

In an embodiment, the analysis system employs the evaluation matrix toassist in producing one or more evaluation ratings for a system, orportion thereof. At a high-level, the analysis system can create fifteenevaluation ratings from the evaluation matrix:

-   -   a sufficiency based understanding evaluation rating,    -   a sufficiency based implementation evaluation rating,    -   a sufficiency based operation evaluation rating,    -   an effectiveness based understanding evaluation rating,    -   an effectiveness based implementation evaluation rating,    -   an effectiveness based operation evaluation rating,    -   a quantity of use based understanding evaluation rating,    -   a quantity of use based implementation evaluation rating,    -   a quantity of use based operation evaluation rating,    -   an appropriate use based understanding evaluation rating,    -   an appropriate use based implementation evaluation rating,    -   an appropriate use based operation evaluation rating,    -   a consistency of use based understanding evaluation rating,    -   a consistency of use based implementation evaluation rating, and    -   a consistency of use based operation evaluation rating.

Each of the fifteen high-level evaluation ratings can be divided into aplurality of lower-level evaluation ratings. For example, a lower levelevaluation rating can be created for each evaluation metric ofprocesses, policies, procedures, certifications, documentation,automation and other measure of the system, or portion thereof. Asanother example, a lower level evaluation rating is created for acombination of evaluation metrics (e.g., processes and policies). As afurther example, a lower level evaluation rating can be created for eachsystem element of the system, each system function of the system, and/oreach security function of the system.

An evaluation rating may be created for an even lower level. Forexample, each process is evaluated to produce its own evaluation rating.As another example, processes regarding a particular objective of thesystem (e.g., software updates) are evaluated to produce an evaluationrating.

FIG. 94 is a schematic block diagram of an embodiment of a sufficiencymodule 610 that includes an evaluation metric counting module 640, acomparison module 641, and an output module 644. Each of the comparisonmodule 641 and the evaluation metric counting module 640 receive atleast some data of the collection of data 581. The sufficiency module610 generates a quantity of evaluation metric indication 620 based onthe data 581 and in accordance with an evaluation perspective (e.g.,understanding, implementation, operation, or self-analysis). Forexample, the sufficiency module generates, for the system (or portionthereof) being evaluated, a quantity of evaluation metric indication 620for:

-   -   understanding of processes (e.g., quantity of all identified        relevant processes compared to an expected quantity of all        relevant processes and/or checklist comparison of identified        relevant processes);    -   processes regarding implementation (e.g., quantity of all        identified relevant processes regarding design and/or build of        the system (or portion thereof) compared to an expected quantity        of all relevant processes regarding design and/or build of the        system (or portion thereof) and/or checklist comparison of        identified relevant processes regarding design and/or build of        the system (or portion thereof));    -   processes regarding operation (e.g., quantity of all identified        relevant processes regarding operation of the system (or portion        thereof) compared to an expected quantity of all relevant        processes regarding operation of the system (or portion thereof)        and/or checklist comparison of identified relevant processes        regarding operation of the system (or portion thereof));    -   processes regarding self-analysis (e.g., quantity of all        identified relevant processes regarding self-analysis of the        system (or portion thereof) compared to an expected quantity of        all relevant processes regarding self-analysis of the system (or        portion thereof) and/or checklist comparison of identified        relevant processes regarding self-analysis of the system (or        portion thereof));    -   understanding of policies;    -   policies regarding implementation;    -   policies regarding operation;    -   policies regarding self-analysis;    -   understanding of procedures;    -   procedures regarding implementation;    -   procedures regarding operation;    -   procedures regarding self-analysis;    -   understanding of certificates;    -   certificates regarding implementation;    -   certificates regarding operation;    -   certificates regarding self-analysis;    -   understanding of documentation;    -   documentation regarding implementation;    -   documentation regarding operation;    -   documentation regarding self-analysis;    -   understanding of automation;    -   automation regarding implementation;    -   automation regarding operation;    -   automation regarding self-analysis;    -   understanding of another evaluation metric;    -   another evaluation metric regarding implementation;    -   another evaluation metric regarding operation; and/or    -   another evaluation metric regarding self-analysis.

For a piece of data that relates to a particular evaluation metric and aparticular evaluation perspective (e.g., understanding of processes),the evaluation metric counting module 640 increments a count. Inaddition, or in the alternative, the comparison module 641 compares thepiece of data to a checklist 643 regarding the particular evaluationmetric and the particular evaluation perspective (e.g., understanding ofprocesses). Note that the checklist is part of, or derived from, thedata analysis parameters 265.

For example, when the piece of data is a process, the comparison module641 determines whether the process is on a process checklist for aparticular evaluation perspective. The comparison module 641 thenrecords the results of the comparison: yes, if the process is on thechecklist or no, if the process is not on the checklist to producechecklist data. As another example, when the piece of data is a policy,the comparison module 641 determines whether the document is on adocument checklist and records the result. As another example, when thepiece of data is a document, the comparison module 641 determines a typeof document (e.g., test result, maintenance record, SW update record,performance data, use data, etc.) and obtains a document type checklist.The comparison module 641 determines whether the document of thespecific type is on a specific type document checklist and records theresult as part of the checklist data.

The output module 644 receives the counts from the evaluation metriccounting module 640 and/or the checklist comparison of the comparisonmodule 640 to produce the quantity of evaluation metric 620. Forexample, the output module 644 receives a count value for each of theevaluation metrics-evaluation perspective combinations and produces thequantity of evaluation metric 620 as an aggregation, combination, or afunction of the individual counts. As a further example, a function isan average function, a mean function, a weighted average, a standarddeviation, and/or other mathematical way to express a set of countvalues.

As another example, the output module 644 receives checklist data foreach of the evaluation metrics-evaluation perspectives. For example, thechecklist data for processes is 10 of 12 processes; the check list datafor policies is 5 of 6 policies; the checklist data for documents is 99of 104 documents; and the checklist data for automation is 3 of 3automations for an evaluation perspective of implementation. For thisexample, the output module 644 produces the quantity of evaluationmetric 620 as an aggregation, combination, or a function of theindividual checklist data. As a further example, a function is anaverage function, a mean function, a weighted average, a standarddeviation, and/or other mathematical way to express a set of checklistdata values.

As another example, the checklist data for processes identifies, for aparticular evaluation perspective, 10 processes found in the collectionof data and identifies 2 processes that were not found in the collectionof data; the checklist data for policies identifies 5 policies found inthe collection of data and identifies 1 policy that was not found in thecollection of data; the checklist data for documents identifies 99documents found in the collection of data and identifies 5 documentsthat were not found in the collection of data; and the checklist datafor automation identifies 3 automations found in the collection of dataand identifies that 0 automations were not found in the collection ofdata. For this example, the output module 644 produces the quantity ofevaluation metric 620 as an aggregation and/or combination of theindividual checklist data for the particular evaluation perspective.

As yet another example, the output module 644 generates, for aparticular evaluation perspective, the quantity of evaluation metric 620from the individual check list data and the individual count of dataregarding an evaluation metric. In this example, the quantity ofevaluation metric 620 is an aggregation and/or combination of theindividual check list data and the individual count of data regarding anevaluation metric.

FIG. 95 is a schematic block diagram of an embodiment of a quantity ofuse module 612 that includes a use counting module 655 and an optionaloutput module 656. The comparison use counting module 655 receive atleast some data of the collection of data 581. The quantity of module612 generates a quantity of use of evaluation metric indication 623based on the data 581 and in accordance with an evaluation perspective(e.g., understanding, implementation, operation, or self-analysis). Forexample, the quantity of module generates, for the system (or portionthereof) being evaluated, a quantity of use of an evaluation metricindication 623 for:

-   -   understanding of processes (e.g., quantity of use of all        identified relevant processes compared to an expected quantity        of all relevant processes);    -   processes regarding implementation (e.g., quantity of use of all        identified relevant processes regarding design and/or build of        the system (or portion thereof) compared to an expected quantity        of all relevant processes regarding design and/or build of the        system (or portion thereof));    -   processes regarding operation (e.g., quantity of use of all        identified relevant processes regarding operation of the system        (or portion thereof) compared to an expected quantity of all        relevant processes regarding operation of the system (or portion        thereof));    -   processes regarding self-analysis (e.g., quantity of use of all        identified relevant processes regarding self-analysis of the        system (or portion thereof) compared to an expected quantity of        all relevant processes regarding self-analysis of the system (or        portion thereof));    -   understanding of policies;    -   policies regarding implementation;    -   policies regarding operation;    -   policies regarding self-analysis;    -   understanding of procedures;    -   procedures regarding implementation;    -   procedures regarding operation;    -   procedures regarding self-analysis;    -   understanding of certificates;    -   certificates regarding implementation;    -   certificates regarding operation;    -   certificates regarding self-analysis;    -   understanding of documentation;    -   documentation regarding implementation;    -   documentation regarding operation;    -   documentation regarding self-analysis;    -   understanding of automation;    -   automation regarding implementation;    -   automation regarding operation;    -   automation regarding self-analysis;    -   understanding of another evaluation metric;    -   another evaluation metric regarding implementation;    -   another evaluation metric regarding operation; and/or another        evaluation metric regarding self-analysis.

For a piece of data that relates to use of a particular evaluationmetric-evaluation perspective combination, the use counting module 655increments a use count for the particular evaluation metric-evaluationperspective combination. As an example of data that relates to use, apiece of data indicates that a process was used (e.g., a log ofpurchasing a SW product in accordance with a software purchase process).As another example of data that relates to use, a piece of dataindicates that a document was use (e.g., the logging of a purchase of aSW product). As yet another example of data that relates to use, a pieceof data indicates that an automation was used (e.g., a log that a SWproduct was automatically updated).

The output module 656, if included, receives the use counts from the usecounting module 655 to produce the quantity of evaluation metric use623. For example, the output module 656 receives a use count value foreach piece of data relating to the use of the evaluationmetric-evaluation perspective combination and produces the quantity ofevaluation metric use 623 as an aggregation, combination, or a functionof the individual use counts. As a further example, a function is anaverage function, a mean function, a weighted average, a standarddeviation, and/or other mathematical way to express a set of countvalues. If the output module 656 is omitted, the use count module 655produces the quantity of evaluation metric use 623.

FIG. 96 is a schematic block diagram of an embodiment of aneffectiveness module 611 that includes a data filter module 650, acontent analysis module 645, an objective analysis module 646, and anobjective output module 647. The effectiveness module 611 generates aquantified effectiveness of evaluation metric indication 622 based onthe data 581 and in accordance with an evaluation perspective (e.g.,understanding, implementation, operation, or self-analysis). Forexample, the effectiveness module generates, for the system (or portionthereof) being evaluated, a quantified effectiveness evaluation metricindication 622 for:

-   -   understanding of processes (e.g., content of all identified        relevant processes compared to an expected content of all        relevant processes);

processes regarding implementation (e.g., content of all identifiedrelevant processes regarding design and/or build of the system (orportion thereof) compared to expected content of all relevant processesregarding design and/or build of the system (or portion thereof));

-   -   processes regarding operation (e.g., content of all identified        relevant processes regarding operation of the system (or portion        thereof) compared to expected content of all relevant processes        regarding operation of the system (or portion thereof));    -   processes regarding self-analysis (e.g., content of all        identified relevant processes regarding self-analysis of the        system (or portion thereof) compared to expected content of all        relevant processes regarding self-analysis of the system (or        portion thereof));    -   understanding of policies;    -   policies regarding implementation;    -   policies regarding operation;    -   policies regarding self-analysis;    -   understanding of procedures;    -   procedures regarding implementation;    -   procedures regarding operation;    -   procedures regarding self-analysis;    -   understanding of certificates;    -   certificates regarding implementation;    -   certificates regarding operation;    -   certificates regarding self-analysis;    -   understanding of documentation;    -   documentation regarding implementation;    -   documentation regarding operation;    -   documentation regarding self-analysis;    -   understanding of automation;    -   automation regarding implementation;    -   automation regarding operation;    -   automation regarding self-analysis;    -   understanding of another evaluation metric;    -   another evaluation metric regarding implementation;    -   another evaluation metric regarding operation; and/or another        evaluation metric regarding self-analysis.

The data filter module 650 filters the collection of data 581 intoevaluation metric data 648 and objectives data 649 based on the dataanalysis parameters 265. The content analysis module 645 producesevaluation metric content data 651 from the evaluation metric data 649.The objective analysis module 646 produces objective content 652 fromthe objectives data 649. The objective output module 647 compares theevaluation metric content data 651 with the object content data 652 toproduce the quantified effectiveness of evaluation metrics 622.

In an embodiment, the content analysis module 645 interprets, for aparticular evaluation perspective, process data of the evaluation metricdata 648 to determine the content of one or more processes (e.g., steps,requirements, etc.) of the data 648 to produce process content data. Thecontent analysis module 645 also interprets, for a particular evaluationperspective, policy data of the evaluation metric data 648 to determinethe content of one or more policies of the data 648 to produce policycontent data. The content analysis module 645 also interprets, for aparticular evaluation perspective, procedure data of the evaluationmetric data 648 to determine the content of one or more procedures ofthe data 648 to produce procedure content data.

The content analysis module 645 also interprets, for a particularevaluation perspective, certification data of the evaluation metric data648 to determine the content of one or more certificates (e.g., issuedby, issue date, expiration date, what's being certified, etc.) of thedata 648 to produce certificate content data. The content analysismodule 645 also interprets, for a particular evaluation perspective,documentation data of the evaluation metric data 648 to determine thecontent of one or more documents (e.g., creation date, creator, subjectmatter, edits, etc.) of the data 648 to produce documentation contentdata. The content analysis module 645 also interprets, for a particularevaluation perspective, automation data of the evaluation metric data648 to determine the content of one or more automations (e.g., triggerevents for an automatic function, nature of the automatic function,supplier of automatic function, etc.) of the data 648 to produceautomation content data.

In an embodiment, the objective output module 647 interprets theobjectives data 649 to produce content for each of the objectives (e.g.,of the guidelines, system requirements, etc.). For example, theobjective analysis module 646 interprets, for a particular evaluationperspective, objective filtered guidelines, system requirements, systemdesign data, system build data, system function data, security functiondata, asset data, and/or supplemental data of the collection of data 581to identify business operation objectives (e.g., corporate objectives,finance objectives, engineering objectives, manufacturing objectives,sales objectives, marketing objectives, etc.) to produce objectivecontent. As a specific example, the objective analysis module 646interprets guideline data to identify a specific manufacturing objectiveof five nines of manufacturing quality.

As further examples, the objective analysis module 646 interpretsobjective filtered guidelines, system requirements, system design data,system build data, system function data, security function data, assetdata, and/or supplemental data of the collection of data 581 to identifydata storage objectives, data use objectives, data transmissionobjectives, data security objectives, data control objectives, datasharing objectives, authorized use objectives, system speed objectives,system hardware architecture objectives, system software architectureobjectives, maintenance requirements objectives, expansion protocolobjectives, etc.

The objective output module 647 aligns, for a particular evaluationperspective, topic related evaluation metric content data 651 withobjective content data 647 to determine how well the evaluation metricdata fulfills the corresponding objective. The determination is acomponent of the quantified effectiveness of evaluation metric 622. Asan example, the specific manufacturing objective of five nines ofmanufacturing quality is aligned with process data, policy data,procedure data, certification data, documentation data, automation data,and/or other metric data regarding manufacturing. The objective outputmodule 647 determines how well the process data, policy data, proceduredata, certification data, documentation data, automation data, and/orother metric data regarding manufacturing fulfill the five nines ofmanufacturing quality objective to produce the quantified effectivenessof evaluation metric 622 with respect to this particular objective.

As a more specific example, the objective output module 647 determineshow well the process data regarding manufacturing address processes forfulfilling the five nines of manufacturing quality objective to producethe quantified effectiveness of processes 622 with respect to thisparticular objective. As another more specific example, the objectiveoutput module 647 determines how well the policy data regardingmanufacturing address policies for fulfilling the five nines ofmanufacturing quality objective to produce the quantified effectivenessof policies 622 with respect to this particular objective. As anothermore specific example, the objective output module 647 determines howwell the procedure data regarding manufacturing address procedures forfulfilling the five nines of manufacturing quality objective to producethe quantified effectiveness of procedures 622 with respect to thisparticular objective.

As another more specific example, the objective output module 647determines how well the certification data regarding manufacturingaddress certifications for fulfilling the five nines of manufacturingquality objective to produce the quantified effectiveness ofcertification 622 with respect to this particular objective. As anothermore specific example, the objective output module 647 determines howwell the documentation data regarding manufacturing addressdocumentation for fulfilling the five nines of manufacturing qualityobjective to produce the quantified effectiveness of documentation 622with respect to this particular objective.

As another more specific example, the objective output module 647determines how well the automation data regarding manufacturing addressautomation for fulfilling the five nines of manufacturing qualityobjective to produce the quantified effectiveness of automation 622 withrespect to this particular objective. As another more specific example,the objective output module 647 determines how well the other metricdata regarding manufacturing address the other metric for fulfilling thefive nines of manufacturing quality objective to produce the quantifiedeffectiveness of the other metric 622 with respect to this particularobjective.

FIG. 97 is a diagram of an example of an effectiveness module producinga quantified effectiveness of an evaluation metric. In this example, theobjective analysis module 646 has identified content of objectives intoinclude (1) all computing devices shall be free of malware; and (2) noharm shall come to the system as a result of malware (e.g., any softwarethat is designed to cause harm to a system such as a virus, worms,Trojan horse, ransomware, spyware, adware, etc.).

The content analysis module 645 has identified a malware process thatincludes two elements: (1) all computing devices shall be regularlytested for the presence of malware; and (2) when malware is detected, itshall be deleted and reported. The objective output module 647 analyzesthe malware process and the two objectives to determine the quantifiedeffective of the process 622-1. The objective output module 647determines that (1) the process meets the objective of computing devicesbeing free of malware; and (2) the process does not address theobjective of no harm shall come to the system.

Assuming a rating scale of 0-10 for each objective, the objective outputmodule 647 would assign a 10 of 10 score for meeting the computingdevices being free of malware and would assign a 0 of 10 score for notaddressing the no harm objective. The objective output module 647processes the two scores to produce a final score for the quantifiedeffectiveness of this process 622-1. For example, the final score is 10of 20 (e.g., a summation function). As another example, the final scoreis 0.5 (e.g., an average function). As another example, the final scoreis 7.5 of 20 (e.g., a weighted average that emphasizes lower scores).

FIG. 98 is a schematic block diagram of an embodiment of an appropriateuse module 613 that includes a data filter module 663, a use specifyanalysis module 660, a use condition analysis module 661, and an outputmodule 662. The appropriate use module 613 generates a quantifiedappropriate use of evaluation metric indication 624 based on the data581 and in accordance with an evaluation perspective (e.g.,understanding, implementation, operation, or self-analysis). Forexample, the appropriate use module generates, for the system (orportion thereof) being evaluated, a quantified appropriate useevaluation metric indication 624 for:

-   -   understanding of processes (e.g., conditions of when identified        relevant processes were used in comparison to expected        conditions as to when relevant processes are to be used);    -   processes regarding implementation (e.g., conditions of when        identified relevant processes regarding design and/or build of        the system (or portion thereof) were used compared to expected        conditions of when relevant processes regarding design and/or        build of the system (or portion thereof) are to be used);    -   processes regarding operation (e.g., conditions of when        identified relevant processes regarding operation of the system        (or portion thereof) were used compared to expected conditions        of relevant processes regarding operation of the system (or        portion thereof) are to be used);    -   processes regarding self-analysis (e.g., conditions of when        identified relevant processes regarding self-analysis of the        system (or portion thereof) were used compared to expected        conditions of relevant processes regarding self-analysis of the        system (or portion thereof) are to be used);    -   understanding of policies;    -   policies regarding implementation;    -   policies regarding operation;    -   policies regarding self-analysis;    -   understanding of procedures;    -   procedures regarding implementation;    -   procedures regarding operation;    -   procedures regarding self-analysis;    -   understanding of certificates;    -   certificates regarding implementation;    -   certificates regarding operation;    -   certificates regarding self-analysis;    -   understanding of documentation;    -   documentation regarding implementation;    -   documentation regarding operation;    -   documentation regarding self-analysis;    -   understanding of automation;    -   automation regarding implementation;    -   automation regarding operation;    -   automation regarding self-analysis;    -   understanding of another evaluation metric;    -   another evaluation metric regarding implementation;    -   another evaluation metric regarding operation; and/or another        evaluation metric regarding self-analysis.

The data filter module 663 filters the collection of data 581 inaccordance with the data analysis parameters to produce evaluationmetric data 664 and use of evaluation metric data 665. The use specifyanalysis module 660 produces, for a particular evaluation perspective,evaluation metric use data 666 (i.e., specified conditions of use forthe evaluation metrics) from the evaluation metric data 664. The usecondition analysis module 661 produces, for a particular evaluationperspective, use condition data 667 (i.e., the recorded conditions ofuse) from the use of evaluation metric data 665 (use data). The outputmodule 662 compares the evaluation metric use data 666 with the usecondition data 652 to produce the quantified appropriate use ofevaluation metric 624 for a particular evaluation perspective.

In an embodiment, the use specify analysis module 660 interprets, for aparticular evaluation perspective, process data of the evaluation metricdata 664 to determine conditions as to when one or more processes shouldbe used. For example, the use specify analysis module 660 determinesthat process 1 is to be used when granting user access privileges forlevel 4 employees. The use specify analysis module 660 also interprets,for a particular evaluation perspective, policy data of the evaluationmetric data 664 to determine conditions as to when one or more policiesshould be used. The use specify analysis module 660 also interprets, fora particular evaluation perspective, procedure data of the evaluationmetric data 664 to determine conditions as to when one or moreprocedures should be used.

The use specify analysis module 660 also interprets, for a particularevaluation perspective, documentation data of the evaluation metric data664 to determine conditions as to when one or more documents should beused (e.g., interpreted, created, edited, signed, etc.). The use specifyanalysis module 660 also interprets, for a particular evaluationperspective, certification data of the evaluation metric data 664 todetermine conditions as to when one or more certificates should be used(e.g., verified, created, updated, signed, etc.). The use specifyanalysis module 660 also interprets, for a particular evaluationperspective, automation data of the evaluation metric data 664 todetermine conditions as to when one or more automations should be used.

The use condition analysis module 661 interprets, for a particularevaluation perspective, the use data 665 to determine the conditionswhen processes here used. For example, process 1 was used for employees7-22 all of whom are level 4 employees and process 1 was used foremployee 74 who is a level 3 employee. The use condition analysis module661 also interprets, for a particular evaluation perspective, the usedata 665 to determine the conditions when policies were used. The usecondition analysis module 661 also interprets, for a particularevaluation perspective, the use data 665 to determine the conditionswhen procedures were used.

The use condition analysis module 661 also interprets, for a particularevaluation perspective, the use data 665 to determine the conditionswhen documents were used. The use condition analysis module 661 alsointerprets, for a particular evaluation perspective, the use data 665 todetermine the conditions when certificates were used. The use conditionanalysis module 661 also interprets, for a particular evaluationperspective, the use data 665 to determine the conditions whenautomations were used.

The output module 662 aligns, for a particular evaluation perspective,conditions of the evaluation metric use content data 666 (i.e.,specified conditions of use for the evaluation metrics) with conditionsof use of the use condition data 667 (i.e., the recorded conditions ofuse) for a given process, policy, procedure, document, certificate,automation, and/or other evaluation metric. The output module 662 theninterprets the specified use conditions for a particular evaluationmetric (e.g., process) in light the actual use conditions for theparticular evaluation metric to produce a quantified appropriate use ofevaluation metric indication 624, or portion thereof, for a particularevaluation perspective.

As an example, the evaluation metric use content data 666 indicates thatprocess 1 is to be used when granting user access privileges for level 4employees. The use condition data 667 indicates that process 1 was usedfor employees 7-22 all of whom are level 4 employees and process 1 wasalso used for employee 74 who is a level 3 employee. The output module662 generates the quantified appropriate use of evaluation metricindication 624, or portion thereof, to reflect that process 1 was usedinappropriately once (e.g., for employee 74) and may further indicatethat process 1 was appropriately used 16 times for employees 7-22. Thequantified appropriate use of evaluation metric indication 624 may be anumerical value (e.g., 1 for inappropriate use; 16/17 for percentage ofappropriate use, 1:16 for a ratio of inappropriate use to appropriateuse, etc.) and/or a text value (e.g., 1 inappropriate use, 16appropriate uses, etc.).

FIG. 99 is a diagram of an example of an appropriate use module 613producing a quantified appropriate of use of an evaluation metric 624-1.In this example, the use specify analysis module 660 identified threeconditions for use of one or more processes. Condition 1 is the dailytesting of all computing devices for the presence of malware. Condition2 is the deleting of malware if it is detected. Condition 3 is thereporting of the testing and its results when testing is completed.

The use condition analysis module 661 interprets security verificationdata to identify uses the of the malware process(es). In this example,the use condition analysis module 661 produced two use condition dataelements. Data element 1 indicates that all computing devices weretested three times on Oct. 1, 2020, no malware was detected, and areport was generated. Data element 2 indicates that all computingdevices were tested on Oct. 2, 2020, one malware was detected anddeleted, and a report was generated. The output module 662 determinesthat (1) the malware process(es) were not appropriately used on Oct. 1,2020 since it was used three times when the condition is daily; and (2)the malware process(es) was appropriately used on Oct. 2, 2020.

Assuming a rating scale of 0-10 for each data element, the output module662 would assign, for example, a 6 of 10 score for data element 1 (e.g.,over used but better than under used) and a 10 of 10 score data element2. The output module 662 processes the two scores to produce a finalscore for the quantified appropriate use of the process(es) 624-1. Forexample, the final score is 15 of 20 (e.g., a summation function). Asanother example, the final score is 0.75 (e.g., an average function). Asanother example, the final score is 12.5 of 20 (e.g., a weighted averagethat emphasizes lower scores).

FIG. 100 is a schematic block diagram of an embodiment of a consistencyof use module 614 that includes a data filter module 673, a use specifyanalysis module 670, a use situation use analysis module 671, and anoutput module 672. The consistency of use module 614 generates aquantified consistency of use of evaluation metric indication 625 basedon the data 581 and in accordance with an evaluation perspective (e.g.,understanding, implementation, operation, or self-analysis). Forexample, the consistency of use module generates, for the system (orportion thereof) being evaluated, a quantified consistency of useevaluation metric indication 625 for:

-   -   understanding of processes (e.g., situations of when identified        relevant processes were used in comparison to expected        situations as to when relevant processes are to be used);    -   processes regarding implementation (e.g., situations of when        identified relevant processes regarding design and/or build of        the system (or portion thereof) were used compared to expected        situations of when relevant processes regarding design and/or        build of the system (or portion thereof) are to be used);    -   processes regarding operation (e.g., situations of when        identified relevant processes regarding operation of the system        (or portion thereof) were used compared to expected situations        of relevant processes regarding operation of the system (or        portion thereof) are to be used);    -   processes regarding self-analysis (e.g., situations of when        identified relevant processes regarding self-analysis of the        system (or portion thereof) were used compared to expected        situations of relevant processes regarding self-analysis of the        system (or portion thereof) are to be used);    -   understanding of policies;    -   policies regarding implementation;    -   policies regarding operation;    -   policies regarding self-analysis;    -   understanding of procedures;    -   procedures regarding implementation;    -   procedures regarding operation;    -   procedures regarding self-analysis;    -   understanding of certificates;    -   certificates regarding implementation;    -   certificates regarding operation;    -   certificates regarding self-analysis;    -   understanding of documentation;    -   documentation regarding implementation;    -   documentation regarding operation;    -   documentation regarding self-analysis;    -   understanding of automation;    -   automation regarding implementation;    -   automation regarding operation;    -   automation regarding self-analysis;    -   understanding of another evaluation metric;    -   another evaluation metric regarding implementation;    -   another evaluation metric regarding operation; and/or    -   another evaluation metric regarding self-analysis.

The data filter module 673 filters the collection of data 581 inaccordance with the data analysis parameters to produce evaluationmetric data 6764 and use of evaluation metric data 675. The use specifyanalysis module 670 produces, for a particular evaluation perspective,evaluation metric specific use data 676 (i.e., specified situation forwhen the evaluation metrics should be used) from the evaluation metricdata 674. The situation use analysis module 671 produces, for aparticular evaluation perspective, situation use data 677 (i.e., therecorded situations of when evaluation metrics were actually used) fromthe use of evaluation metric data 675 (use data). The output module 672compares the evaluation metric specific use data 676 with the situationuse data 677 to produce the quantified consistency of use of evaluationmetric indication 625 for a particular evaluation perspective.

In an embodiment, the use specify analysis module 670 interprets, for aparticular evaluation perspective, process data of the evaluation metricdata 674 to determine situations as to when one or more processes shouldbe used. For example, the use specify analysis module 670 determinesthat use of process 1, which is regarding granting user accessprivileges for level 4 employees, was to be used for employees 1-22. Theuse specify analysis module 670 also interprets, for a particularevaluation perspective, policy data of the evaluation metric data 674 todetermine situations as to when one or more policies should be used. Theuse specify analysis module 670 also interprets, for a particularevaluation perspective, procedure data of the evaluation metric data 674to determine situations as to when one or more procedures should beused.

The use specify analysis module 670 also interprets, for a particularevaluation perspective, documentation data of the evaluation metric data674 to determine situations as to when one or more documents should beused (e.g., interpreted, created, edited, signed, etc.). The use specifyanalysis module 670 also interprets, for a particular evaluationperspective, certification data of the evaluation metric data 674 todetermine situations as to when one or more certificates should be used(e.g., verified, created, updated, signed, etc.). The use specifyanalysis module 670 also interprets, for a particular evaluationperspective, automation data of the evaluation metric data 674 todetermine situations as to when one or more automations should be used.

The situation use analysis module 671 interprets, for a particularevaluation perspective, the use data 675 to determine the situations asto when processes should be used. For example, process 1 was used togrant access employees 7-22 all of whom are level 4 employees. Thesituation use analysis module 671 also interprets, for a particularevaluation perspective, the use data 675 to determine the situationswhen policies were used. The situation use analysis module 671 alsointerprets, for a particular evaluation perspective, the use data 675 todetermine the situations when procedures were used.

The situation use analysis module 671 also interprets, for a particularevaluation perspective, the use data 675 to determine the situationswhen documents were used. The situation use analysis module 671 alsointerprets, for a particular evaluation perspective, the use data 675 todetermine the situations when certificates were used. The situation useanalysis module 671 also interprets, for a particular evaluationperspective, the use data 675 to determine the situations whenautomations were used. Note that the situation use analysis module 671functions similarly to the use condition analysis module 661 of theappropriate use module 614.

The output module 672 aligns, for a particular evaluation perspective,situations of the evaluation metric use content data 676 (i.e.,specified conditions of when evaluation metric data should be used) withsituations of use of the situation use data 677 (i.e., the recordedsituations of use) for a given process, policy, procedure, document,certificate, automation, and/or other evaluation metric. The outputmodule 672 then interprets, for a particular evaluation perspective, thespecified use situations for a particular evaluation metric (e.g.,process) in light the actual use situations for the particularevaluation metric to produce a quantified consistency of use ofevaluation metric indication 625, or portion thereof.

As an example, the evaluation metric use content data 676 indicates thatprocess 1, which is regarding granting user access privileges for level4 employees, was to be used to grant access to employees 1-22. Thesituation use data 677 indicates that process 1 was used for employees7-22 all of whom are level 4 employees. The output module 672 generatesthe quantified consistency of use of evaluation metric indication 625,or portion thereof, to reflect that process 1 was used inconsistently(e.g., was not used for employees 1-6, but was used for employees 7-22).The quantified consistency of use of evaluation metric indication 625may be a numerical value (e.g., 6 for missing uses; 16/22 for percentageof consistent use, 6:16 for a ratio of missing use to actual use, etc.)and/or a text value (e.g., 6 missing uses, 16 actually uses, etc.).

FIG. 101 is a diagram of an example of a consistency of use module 614producing a quantified consistency of use of an evaluation metric 625-1.In this example, the use specify analysis module 670 identified threesituations for use of one or more processes. Situation 1 is the allcomputing devices are to be tested daily for the presence of malware.Situation 2 is that any malware found is to be deleted. Situation 3 isthat all testing and findings regarding malware is to be reported.

The situation use analysis module 671 interprets security verificationdata to identify uses the of the malware process(es). In this example,the situation use analysis module 671 produced two use condition dataelements. Data element 1 indicates that all computing devices weretested three times on Oct. 1, 2020, no malware was detected, but areport was not generated. Data element 2 indicates that all computingdevices were tested on Oct. 2, 2020, one malware was detected anddeleted, and a report was generated. The output module 672 determinesthat (1) the malware process(es) were not consistently used since areport was not generated on Oct. 1, 2020.

Assuming a rating scale of 0-10 for each expected use of a malwareprocess. For this example, there are six expected uses: test, delete iffound, and report for each of the two day. Since, on Oct. 1, 2020 areport was not generated, this expected process would receive a 0 of 10score. If part of the report were generated, but not a full report, thescore would be greater than 0 of 10, but less than 10 of 10. The otherexpected uses would receive a 10 of 10 score since they were used asexpected and fully. The output module 672 processes the six scores toproduce a final score for the quantified consistency of use of theprocess(es) 625-1. For example, the final score is 50 of 60 (e.g., asummation function). As another example, the final score is 0.833 (e.g.,an average function). As another example, the final score is 45 of 60(e.g., a weighted average that emphasizes lower scores).

FIG. 102 is a schematic block diagram of an embodiment of anunderstanding, implementation, operation, or self-analysis module616-619 configured to process the quantity of evaluation metricindicator 620. The module 616-619 includes a comparator 680, a quantityreference generator 682, a rating generator 681, and a reference scalegenerator 683. As previously discussed, the quantity of evaluationmetric indicator 620 is based on a count of evaluation metric data(e.g., a count of processes, a count of policies, etc.) and/or based ona checklist of evaluation metric data (e.g., a checklist of processes, achecklist of policies, etc.).

In an example, the quantity reference generator 682 generates areference quantity 683 based on evaluation input(s) (e.g., evaluationviewpoint of disclosed data, discovered data, and/or desired data;evaluation metric of process, policy, procedure, documentation,certification, automation, and/or other metric; evaluation modality ofsufficiency, effectiveness, quantity of use, appropriate use, and/orconsistency of use; characteristics of the system that include size,capacity, etc., and/or evaluation category of identify, protect, detect,respond, and/or recover). An example of generating a reference quantity683 for a count based evaluation is discussed with reference to FIG. 104. An example of generating a reference quantity 683 for a checklistbased evaluation is discussed with reference to FIG. 107 .

The comparator 680 compares the quantity of evaluation metric indicator620 associated with a particular evaluation perspective (e.g.,understanding, implementation, operation, or self-analysis) with thereference quantity 638 to produce a comparison output 684. For example,the comparator compares a count of processes (e.g., 12) for theevaluation perspective of understanding with an understanding referencequantity of processes (e.g., 13) to produce a comparison output 684(e.g., one less process than expected). As another example, thecomparator compares a list of processes with an understanding referencequantity checklist of processes to produce a comparison output 684(e.g., all identified processes in the list are on the checklist). Asanother example, the comparator compares a count of processes (e.g., 8)for the evaluation perspective of implementation with an implementationreference quantity of processes (e.g., 8) to produce a comparison output684 (e.g., have the expected number of implementation relatedprocesses).

The reference generator 683 generates a reference scale 626 based on theevaluation input(s). For example, the reference generator 683 generatesa reference scale for processes for a particular evaluation perspective.As another example, the reference generator 683 generates a referencescale for processes regarding implementation for the evaluation categoryof identify. As another example, the reference generator 683 generates areference scale for documentation regarding operation for the evaluationcategory of identify from disclosed data. Further examples of referencescales are provided with reference to FIGS. 105 and 108 .

The rating generator 681 generates an evaluation rating 627 regarding anevaluation metric-evaluation perspective combination. Based on theprevious example, the compare output 684 indicates that the count ofidentified processes within the collection of data was one less thanexpected for understanding and indicates that, for implementation, thequantity of processes was as expected. The rating generator 681 maps thecompare output 626 (e.g., one less process than expected and as expectedfor understanding) to the reference scale 626 (e.g., a bell shaped curvehaving a scale for one or more of the evaluation metric-evaluationperspective combinations) to produce the evaluation rating 627 forprocesses. Further examples of generating the evaluation rating areprovided with reference to FIGS. 106 and 109 .

FIG. 103 is a logic diagram of an example of a module of FIG. 102generating an evaluation metric rating. The method includes step 685where the module receives one or more evaluation inputs (e.g.,evaluation viewpoint, evaluation modality, evaluation category, systemcharacteristics, and/or evaluation metric). The method continues atsteps 686 and 689. At step 686, the module determines a referencequantity based on the evaluation input(s). At step 689, the moduledetermines a reference scale based on the evaluation input(s).

The method further includes step 688 where the module receives aquantity of evaluation metric indication (e.g., a result of a count ofprocesses, a result of a checklist of processes, etc.). The methodcontinues at step 687 where the module produces a compare output basedon the quantity of evaluation metric indication and the referencequantity. The method continues at step 690 where the module generates anevaluation rating for an evaluation metric based on the compare outputand the reference scale.

FIG. 104 is a logic diagram of an example of a method performed by thequantity reference generator of a module of FIG. 102 to generate areference quantity for a count based analysis. The method includes step691 where the module determines whether the evaluation rating is to begenerated based on disclosed data, discovered data, or based on acomparison disclosed, discovered, and/or desired data. When theevaluation rating is to be generated based on disclosed data ordiscovered data, the method continues at step 692 where the moduledetermines to use an optimal count measure or a conventional countmeasure. For example, an optimal count measure corresponds to anexpected number of processes, policies, procedures, documents,certificates, automations, and/or other metrics for a state of the artsystem of like characteristics. As another example, a conventional countcorresponds to an expected number of processes, policies, procedures,documents, certificates, automations, and/or other metrics for aconventional system of like characteristics.

When the optimal count measure is not to be used, the method continuesat step 693 where the module determines a convention quantity for one ormore evaluation metrics (e.g., 15 processes, 5 policies, 23 procedures,78 documents, 11 certificates, 3 automations, and/or 7 other metrics).When the optimal count measure is to be used, the method continues atstep 694 where the module determines an optimal quantity for one or moreevaluation metrics (e.g., 18 processes, 8 policies, 32 procedures, 124documents, 19 certificates, 2 automations, and/or 22 other metrics).

When the evaluation rating is to be based on a comparison disclosed,discovered, and/or desired data, the method continues at step 695 wherethe module determines whether the evaluation is to be based on acomparison of disclosed to discovered data. If yes, the method continuesat step 696 where the module determines a quantity of evaluation metricbased on the discovered data for using in comparison to a quantity ofevaluation metric of the disclosed data.

If the comparison is not for disclosed to discovered, the methodcontinues at step 697 where the module determines whether the comparisonis for disclosed to desired. If yes, the method continues at step 698where the module determines a quantity of evaluation metric based on thedesired data for using in comparison to a quantity of evaluation metricof the disclosed data. If not, the method continues at step 699 wherethe module determines a quantity of evaluation metric based on thedesired data for using in comparison to a quantity of evaluation metricof the discovered data.

FIG. 105 is a diagram of an example of a quantity reference scale 689that in a graph plotting a scale versus a deviation (deviation ofquantity indication inputted from the reference quantity) The curve isbell shaped with zero deviation at the center of the bell curve. Thecurve could be symmetrical about the center or asymmetrical about thecenter (e.g., sharper curve when less than zero deviation in comparisonto when greater than zero deviation). The scale value has two or morevalues to provide a desired level of granularity in the evaluationrating. In this example, the scale ranges from 0 to 50.

FIG. 106 is a logic diagram of an example of a method performed by arating generator of FIG. 102 to generate an evaluation metric rating fora count based evaluation. The method begins a step 688, 686, and 689. Atstep 688, the module receives a quantity of evaluation metric indicationof “X”. At step 686, the module receives the reference quantity of “Y”.At step 689, the module receives the reference scale (e.g., 0-50).

From steps 688 and 686, the method continues at step 687 where themodule determine a deviation by comparing X and Y (e.g., Y−X=deviation).The method continues at step 690 where the module maps the deviation tothe reference scale. For example, if the deviation is zero, theevaluation metric rating is 50. The more the deviation deviates from thezero, the lower the rating.

FIG. 107 is a logic diagram of an example of a method performed by thequantity reference generator of a module of FIG. 102 to generate areference quantity for a checklist based analysis. The method includesstep 700 where the module determines whether the evaluation rating is tobe generated based on disclosed data, discovered data, or based on acomparison disclosed, discovered, and/or desired data. When theevaluation rating is to be generated based on disclosed data ordiscovered data, the method continues at step 701 where the moduledetermines to use an optimal checklist or a conventional checklist. Forexample, an optimal checklist corresponds to a checklist for each ofprocesses, policies, procedures, documents, certificates, automations,and/or other metrics for a state of the art system of likecharacteristics. As another example, a conventional checklistcorresponds to a checklist for each of processes, policies, procedures,documents, certificates, automations, and/or other metrics for aconventional system of like characteristics.

When the optimal checklist is not to be used, the method continues atstep 702 where the module determines a convention checklist for one ormore evaluation metrics. When the optimal checklist is to be used, themethod continues at step 703 where the module determines an optimalchecklist for one or more evaluation metrics.

When the evaluation rating is to be based on a comparison disclosed,discovered, and/or desired data, the method continues at step 704 wherethe module determines whether the evaluation is to be based on acomparison of disclosed to discovered data. If yes, the method continuesat step 705 where the module determines a checklist of evaluation metricbased on the discovered data for using in comparison to the identifiedevaluation metric of the disclosed data.

If the comparison is not for disclosed to discovered, the methodcontinues at step 706 where the module determines whether the comparisonis for disclosed to desired. If yes, the method continues at step 707where the module determines a checklist of evaluation metric based onthe desired data for using in comparison to identified evaluation metricof the disclosed data. If not, the method continues at step 708 wherethe module determines a checklist of evaluation metric based on thedesired data for using in comparison to identified evaluation metric ofthe discovered data.

FIG. 108 is a diagram of an example of a quantity reference scale 689that in a graph plotting a scale versus a deviation (deviation ofidentified evaluation metric from the checklist for the evaluationmetric). The curve is bell shaped with zero deviation at the center ofthe bell curve. The curve could be symmetrical about the center orasymmetrical about the center (e.g., sharper curve when less than zerodeviation in comparison to when greater than zero deviation). The scalevalue has two or more values to provide a desired level of granularityin the evaluation rating. In this example, the scale ranges from 0 to50.

FIG. 109 is a logic diagram of an example of a method performed by arating generator of FIG. 102 to generate an evaluation metric rating fora checklist based evaluation. The method begins a step 688-1, 686-1, and689-1. At step 688-1, the module receives a checklist of evaluationmetric indication of “X”. At step 686-1, the module receives thereference checklist of “Y”. At step 689-1, the module receives thereference scale (e.g., 0-50).

From steps 688-1 and 686-1, the method continues at step 687-1 where themodule determine a deviation by comparing X and Y (e.g., Y−X=deviation).The method continues at step 690-1 where the module maps the deviationto the reference scale. For example, if the deviation is zero, theevaluation metric rating is 50. The more the deviation deviates from thezero, the lower the rating.

FIG. 110 is a schematic block diagram of an embodiment of anunderstanding, implementation, operation, or self-analysis module616-619 for processing the quantified effectiveness of evaluation metricindication 622. In this embodiment, the module 616-619 includes thereference scale generator 683 and the rating generator 681.

The reference generator 683 generates a reference scale 626 based on oneor more evaluation inputs (e.g., one or more evaluation viewpoints; oneor more evaluation metrics; one or more evaluation modalities; one ormore characteristics of the system; and/or one or more evaluationcategories). For example, the reference scale generator 683 generates areference scale for evaluating processes of: none for a rating of 0;inconsistent for a rating of 10; repeatable for a rating of 20;standardized for a rating of 30; measured for a rating of 40; andoptimized for rating of 50.

In this example, a level of “none” on the reference scale for processescorresponds to zero or near zero effectiveness of the processes toreliably, repeatedly, and/or completely indicate that the system, orportion thereof, fulfills the objectives of the system, or portionthereof, (e.g., some to all of guidelines, system requirements, systemdesign, system build, and/or system operation). Continuing with thisexample, a level of “inconsistent” on the reference scale for processescorresponds to low level of effectiveness of the processes to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof. Asan example of inconsistent, there are processes but they has gaps intheir content, which produces inconsistent indications of fulfilling theobjectives. As another example of inconsistent, the content of one ormore processes is inconsistent (e.g., contradicts, produces an infiniteloop, creates a deadlock, etc.) with content of one or more other theprocesses, which produces inconsistent indications of fulfilling theobjectives.

Continuing with this example, a level of “repeatable” on the referencescale for processes corresponds to low to mid level of effectiveness ofthe processes to reliably, repeatedly, and/or completely indicate thatthe system, or portion thereof, fulfills the objectives of the system,or portion thereof. As an example of repeatable, the content of theprocesses produce repeatable indications of fulfilling at least some ofthe objectives, or portions thereof, but the processes are static (notregularly reviewed, not regularly updated, etc.), having varying degreesof specificity, are more generic in nature than specific to the system,and/or are not created in a consistent manner.

Continuing with this example, a level of “standardized” on the referencescale for processes corresponds to mid-level of effectiveness of theprocesses to reliably, repeatedly, and/or completely indicate that thesystem, or portion thereof, fulfills the objectives of the system, orportion thereof. As an example of standardized, the content of theprocesses produce repeatable indications of fulfilling at least some ofthe objectives, or portions thereof, and are created in a consistent(e.g., standardized) manner, but the processes are static (not regularlyreviewed, not regularly updated, etc.), having varying degrees ofspecificity, and/or are more generic in nature than specific to thesystem.

Continuing with this example, a level of “measured” on the referencescale for processes corresponds to mid to high level of effectiveness ofthe processes to reliably, repeatedly, and/or completely indicate thatthe system, or portion thereof, fulfills the objectives of the system,or portion thereof. As an example of measured, the content of theprocesses produce repeatable indications of fulfilling at least some ofthe objectives, or portions thereof, the processes are created in aconsistent manner, have consistent specificity, and are specific to thesystem, but the processes are static (not regularly reviewed, notregularly updated, etc.).

Continuing with this example, a level of “optimized” on the referencescale for processes corresponds to high level of effectiveness of theprocesses to reliably, repeatedly, and/or completely indicate that thesystem, or portion thereof, fulfills the objectives of the system, orportion thereof. As an example of optimized, the content of theprocesses produce repeatable indications of fulfilling at least some ofthe objectives, or portions thereof, the processes are created in aconsistent manner, have consistent specificity, are specific to thesystem, and are dynamic (regularly reviewed, regularly updated, etc.).

The reference scale generator 683 generates a reference scale forevaluating policies. As an example, the reference scale includes: nonefor a rating of 0; informal for a rating of 5; defined for a rating of10; audited for a rating of 15; and embedded for a rating of 20. In thisexample, a level of “none” on the reference scale for policiescorresponds to zero or near zero effectiveness of the policies toreliably, repeatedly, and/or completely indicate that the system, orportion thereof, fulfills the objectives of the system, or portionthereof.

Continuing with this example, a level of “informal” on the referencescale for policies corresponds to low level of effectiveness of thepolicies to reliably, repeatedly, and/or completely indicate that thesystem, or portion thereof, fulfills the objectives of the system, orportion thereof. As an example of informal, there are no formalrequirements for creation, maintenance, and/or application of content ofpolicies. As another example of informal, the policies have gaps intheir content, which produces inconsistent indications of fulfilling theobjectives.

Continuing with this example, a level of “defined” on the referencescale for policies corresponds to low to mid level of effectiveness ofthe policies to reliably, repeatedly, and/or completely indicate thatthe system, or portion thereof, fulfills the objectives of the system,or portion thereof. As an example of defined, there are formalrequirements for content creation of policies and the policies producemostly consistent results, but there are no, or limited, formalrequirements for content maintenance of policies and/or contentapplication of policies.

Continuing with this example, a level of “audited” on the referencescale for policies corresponds to mid to high level of effectiveness ofthe policies to reliably, repeatedly, and/or completely indicate thatthe system, or portion thereof, fulfills the objectives of the system,or portion thereof. As an example of audited, there are formalrequirements for content creation of policies and for contentapplication of the policies, the policies produce consistent results,but there is no, or limited, formal requirements for content maintenanceof policies.

Continuing with this example, a level of “embedded” on the referencescale for policies corresponds to high level of effectiveness of thepolicies to reliably, repeatedly, and/or completely indicate that thesystem, or portion thereof, fulfills the objectives of the system, orportion thereof. As an example of embedded, there are formalrequirements for content creation of policies, for content applicationof the policies, and for content maintenance of policies. Further, thepolicies produce consistent results.

As another example, the reference scale generator 683 generates areference scale for evaluating documents of: none for a rating of 0;informal for a rating of 5; formal for a rating of 10; metric &reporting for a rating of 15; and improvement for a rating of 20. Inthis example, a level of “none” on the reference scale for documentscorresponds to zero or near zero effectiveness of the documents toreliably, repeatedly, and/or completely indicate that the system, orportion thereof, fulfills the objectives of the system, or portionthereof.

Continuing with this example, a level of “informal” on the referencescale for documents corresponds to low level of effectiveness of thedocuments to reliably, repeatedly, and/or completely indicate that thesystem, or portion thereof, fulfills the objectives of the system, orportion thereof. As an example of informal, there are no formalrequirements for creation, maintenance, and/or application of content ofdocuments. As another example of informal, the documents have gaps intheir content, which produces inconsistent indications of fulfilling theobjectives.

Continuing with this example, a level of “formal” on the reference scalefor documents corresponds to low to mid level of effectiveness of thedocuments to reliably, repeatedly, and/or completely indicate that thesystem, or portion thereof, fulfills the objectives of the system, orportion thereof. As an example of defined, there are formal requirementsfor content creation of documents, but there are no, or limited, formalrequirements for content maintenance of documents and/or contentapplication of documents.

Continuing with this example, a level of “metric & reporting” on thereference scale for documents corresponds to mid to high level ofeffectiveness of the documents to reliably, repeatedly, and/orcompletely indicate that the system, or portion thereof, fulfills theobjectives of the system, or portion thereof. As an example of metric &reporting, there are formal requirements for content creation ofdocuments and for content application of the documents, the documentsproduce consistent results, but there is no, or limited, formalrequirements for content maintenance of documents.

Continuing with this example, a level of “improvement” on the referencescale for documents corresponds to high level of effectiveness of thedocuments to reliably, repeatedly, and/or completely indicate that thesystem, or portion thereof, fulfills the objectives of the system, orportion thereof. As an example of improvement, there are formalrequirements for content creation of documents, for content applicationof the documents, and for content maintenance of policies.

As another example, the reference scale generator 683 generates areference scale for evaluating automation of: unavailable for a ratingof 10; none for a rating of 0; partial for a rating of 5; and full for arating of 10. In this example, a level of “unavailable” for automationcorresponds to automation for a particular incident (e.g., automation ofa feature of the system) is not available. Continuing with this example,a level of “none” on the reference scale for automation corresponds tozero or near zero effectiveness of evaluating automation of the system,or portion thereof.

Continuing with this example, a level of “partial” on the referencescale for automation corresponds to mid-level effectiveness ofevaluating automation of the system, or portion thereof. Continuing withthis example, a level of “full” on the reference scale for automationcorresponds to high level effectiveness of evaluating automation of thesystem, or portion thereof.

The reference scale generator 683 generates a reference scale forevaluating procedures of: none for a rating of 0; informal for a ratingof 5; defined for a rating of 10; audited for a rating of 15; andembedded for a rating of 20. The reference scale generator 683 alsogenerates a reference scale for evaluating certificates of: none for arating of 0; informal for a rating of 5; forma for a rating of 10;metric & reporting for a rating of 15; and improvement for a rating of20.

The rating generator 681 generates the evaluation rating 627 for thequantified effectiveness of the evaluation metric indicator 622 based onthe reference scale 626. For each of the evaluation metrics, the ratinggenerator 681 maps the quantified effectiveness of the evaluation metricto the reference scale 626. As an example, the rating generator 681 mapsthe quantified effectiveness of processes to the process reference scale626. In this example, the quantified effectiveness of processes includesan indication for repeatability of the processes, process contentcreation consistency, consistency of process content specificity (e.g.,processes are about equally detailed and/or are all appropriatelydetailed), a balance of generic polices to system specific policies,and/or a balance of static policies to dynamic policies. Additionalexamples are provided with reference to FIGS. 111-116 .

FIG. 111 is a logic diagram of an example of a module of FIG. 110generating an evaluation metric rating. The method begins at step 710where the module evaluates the quantified effectiveness of processes todetermine whether there is at least one process in the collection ofdata. Note that the threshold number in this step could be greater thanone. If there are no processes, the method continues at step 711 wherethe module generates a process rating of 0 (and/or a word rating of“none”).

If there is at least one process, the method continues at step 712 wherethe module determines whether the content of the processes arerepeatable. As a further and/or alternative example, repeatable includescontent of processes produce consistent results, content detailvariations from process to process, content is not routinely reviewed inan organized manner, and/or the content is not regulated.

If the content of the processes are not repeatable, the method continuesat step 713 where the module generates a process rating of 10 (and/or aword rating of “inconsistent”). If, however, the content of processesare at least repeatable, the method continues at step 714 where themodule determines whether the content of the processes is standardized.As a further and/or alternative example, standardized includesrepeatable plus there are no appreciable variations in detail of contentof the processes from process to process, and/or the content of theprocesses are regulated.

If the content of the processes is not standardized, the methodcontinues at step 715 where the module generates a process rating of 20(and/or a word rating of “repeatable”). If, however, the content of theprocesses are at least standardized, the method continues at step 716where the module determines whether the content of the processes ismeasured. As a further and/or alternative example, measured includesstandardized plus precise, exact, and/or content calculated to specificneeds, concerns, and/or functioning of the system.

If the content of the processes is not measured, the method continues atstep 717 where the module generates a process rating of 30 (and/or aword rating of “standardized”). If, however, the content of theprocesses is at least measured, the method continues at step 718 wherethe module determines whether the content of the processes is optimized.As a further and/or alternative example, optimized includes measuredplus content of the processes are up-to-date and/or improvement of thecontent of the process is assessed on a regular basis as part of systemprotocols.

If the content of the processes is not optimized, the method continuesat step 719 where the module generates a process rating of 40 (and/or aword rating of “measured”). If the content of the processes isoptimized, the method continues at step 720 where the module generates aprocess rating of 50 (and/or a word rating of “optimized”). Note thatthe numerical rating are example values and could be other values.Further note that the number of level of process rating may be more orless than the six shown.

FIG. 112 is a logic diagram of a further example of a module of FIG. 110generating a policy evaluation rating. The method begins at step 721where the module determines whether there is at least one policy in thecollection of data. Note that the threshold number in this step could begreater than one. If there are no policies, the method continues at step722 where the module generates a policy rating of 0 (and/or a wordrating of “none”).

If there is at least one policy, the method continues at step 723 wherethe module determines whether content of the policies is defined. As afurther and/or alternative example, defined content of policies includesufficient detail to produce consistent results, include content detailvariations from policy to policy, content of the policies is notroutinely reviewed in an organized manner, and/or content of thepolicies is not all regulated.

If the content of the policies is not defined, the method continues atstep 724 where the module generates a policy rating of 5 (and/or a wordrating of “informal”). If, however, the content of the policies is atleast defined, the method continues at step 725 where the moduledetermines whether the policies are audited. As a further and/oralternative example, audited includes defined plus the content of thepolicies is routinely reviewed, and/or the content of the policies isregulated.

If the content of the policies is not audited, the method continues atstep 726 where the module generates a policy rating of 10 (and/or a wordrating of “defined”). If, however, the content of the policies is atleast audited, the method continues at step 727 where the moduledetermines whether the content of the policies is embedded. As a furtherand/or alternative example, embedded includes audited plus the contentof the policies is systematically rooted in most, if not all, aspects ofthe system.

If the content of the policies is not embedded, the method continues atstep 728 where the module generates a policy rating of 15 (and/or a wordrating of “audited”). If the policies are embedded, the method continuesat step 729 where the module generates a policy rating of 20 (and/or aword rating of “embedded”). Note that the numerical rating are examplevalues and could be other values. Further note that the number of levelof policy rating may be more or less than the five shown.

FIG. 113 is a logic diagram of a further example of a module of FIG. 110generating a policy evaluation rating. The method begins at step 730where the module determines whether there is at least one document inthe collection of data. Note that the threshold number in this stepcould be greater than one. If there are no documents, the methodcontinues at step 731 where the module generates a documentation ratingof 0 (and/or a word rating of “none”).

If there is at least one document, the method continues at step 732where the module determines whether the documents are formalized. As afurther and/or alternative example, formalized documents includesufficient detail to produce consistent documentation, there will likelybe variations from document to document, the documents are not routinelyreviewed in an organized manner, and/or formation of documents is notregulated.

If the documents are not formalized, the method continues at step 733where the module generates a documentation rating of 5 (and/or a wordrating of “informal”). If, however, the documents are at leastformalized, the method continues at step 734 where the module determineswhether the documents are metric & reporting. As a further and/oralternative example, metric & reporting includes formal plus thedocuments are routinely reviewed, and/or the formation of documents isregulated.

If the documents are not metric & reporting, the method continues atstep 735 where the module generates a documentation rating of 10 (and/ora word rating of “formal”). If, however, the documents are at leastmetric & reporting, the method continues at step 743 where the moduledetermines whether the documents are improvement. As a further and/oralternative example, improvement includes metric & reporting plusdocument formation is systematically rooted in most, if not all, aspectsof the system.

If the documents are not improvement, the method continues at step 737where the module generates a documentation rating of 15 (and/or a wordrating of “metric & reporting”). If the documents are improvement, themethod continues at step 738 where the module generates a documentationrating of 20 (and/or a word rating of “improvement”). Note that thenumerical rating are example values and could be other values. Furthernote that the number of level of documentation rating may be more orless than the five shown.

FIG. 114 is a logic diagram of a further example of a module of FIG. 110generating an automation evaluation rating. The method begins at step739 where the module determines whether there is available automationfor a particular system aspect, system criteria, system features, and/orsystem mode. If automation is not available, the method continues atstep 740 where the module generates an automation rating of 10 (and/or aword rating of “unavailable”).

If automation is available (e.g., there are particular system featuresthat can be automated), the method continues at step 741 where themodule determines whether there is at least one automation in the data.If not, the method continues at step 742 where the module generates anautomation rating of 0 (and/or a word rating of “none”).

If there is at least one automation, the method continues at step 743where the module determines whether full automation is found in thedata. As a further and/or alternative example, full automation refers tothe automation techniques that are available for the system are in thedata and the automations are effective (e.g., there is automation forthe particular features that can have automation and the automationswork as intended).

If the automation is not full, the method continues at step 744 wherethe module generates an automation rating of 5 (and/or a word rating of“partial”). If, however, the automation is full, the method continues atstep 745 where the module generates an automation rating of 10 (and/or aword rating of “full”). Note that the numerical rating are examplevalues and could be other values. Further note that the number of levelof automation may be more or less than the four shown.

FIG. 115 is a logic diagram of a further example of a module of FIG. 110generating a procedure evaluation rating. In this example, the moduleuses a reference scale that is similar to the reference scales as wasused for policies, but a different reference scale could be use. Themethod begins at step 746 where the module determines whether there isat least one procedure in the collection of data. Note that thethreshold number in this step could be greater than one. If there are noprocedures, the method continues at step 747 where the module generatesa procedure rating of 0 (and/or a word rating of “none”).

If there is at least one procedure, the method continues at step 748where the module determines whether content of the procedures isdefined. As a further and/or alternative example, defined content ofprocedures include sufficient detail to produce consistent results,include content detail variations from procedure to procedure, contentof the procedures is not routinely reviewed in an organized manner,and/or content of the procedures is not all regulated.

If the content of the procedures is not defined, the method continues atstep 749 where the module generates a procedure rating of 5 (and/or aword rating of “informal”). If, however, the content of the proceduresis at least defined, the method continues at step 750 where the moduledetermines whether the procedures are audited. As a further and/oralternative example, audited includes defined plus the content of theprocedures is routinely reviewed, and/or the content of the proceduresis regulated.

If the content of the procedures is not audited, the method continues atstep 751 where the module generates a procedure rating of 10 (and/or aword rating of “defined”). If, however, the content of the procedures isat least audited, the method continues at step 752 where the moduledetermines whether the content of the procedures is embedded. As afurther and/or alternative example, embedded includes audited plus thecontent of the procedures is systematically rooted in most, if not all,aspects of the system.

If the content of the procedures is not embedded, the method continuesat step 753 where the module generates a procedure rating of 15 (and/ora word rating of “audited”). If the procedures are embedded, the methodcontinues at step 754 where the module generates a procedure rating of20 (and/or a word rating of “embedded”). Note that the numerical ratingare example values and could be other values. Further note that thenumber of level of procedure rating may be more or less than the fiveshown.

FIG. 116 is a logic diagram of a further example of a module of FIG. 110generating a certification evaluation rating. In this example, themodule uses a reference scale that is similar to the reference scales aswas used for documentation, but a different reference scale could beuse. The method begins at step 755 where the module determines whetherthere is at least one certificate in the collection of data. Note thatthe threshold number in this step could be greater than one. If thereare no certificates, the method continues at step 756 where the modulegenerates a certification rating of 0 (and/or a word rating of “none”).

If there is at least one certificate, the method continues at step 757where the module determines whether the certificates are formalized. Asa further and/or alternative example, formalized certificates includesufficient detail to obtain and/or verify consistent certification,there will likely be variations in the detail for obtaining and/orverifying certificates, the manner of obtaining and/or verifyingcertificates are not routinely reviewed in an organized manner, and/ormanner of obtaining and/or verifying certificates are not regulated.

If the certificates are not formalized, the method continues at step 758where the module generates a certification rating of 5 (and/or a wordrating of “informal”). If, however, the certificates are at leastformalized, the method continues at step 759 where the module determineswhether the certificates are metric & reporting. As a further and/oralternative example, metric & reporting includes formal plus the mannerof obtaining and/or verifying certificates are routinely reviewed,and/or the manner of obtaining and/or verifying certificates areregulated.

If the documents are not metric & reporting, the method continues atstep 760 where the module generates a certification rating of 10 (and/ora word rating of “formal”). If, however, the certificates are at leastmetric & reporting, the method continues at step 761 where the moduledetermines whether the certificates are improvement. As a further and/oralternative example, improvement includes metric & reporting plus themanner of obtaining and/or verifying certificates is systematicallyrooted in most, if not all, aspects of the system.

If the certificates are not improvement, the method continues at step762 where the module generates a certificate rating of 15 (and/or a wordrating of “metric & reporting”). If the certificates are improvement,the method continues at step 763 where the module generates acertification rating of 20 (and/or a word rating of “improvement”). Notethat the numerical rating are example values and could be other values.Further note that the number of level of certification rating may bemore or less than the five shown.

FIG. 117 is a schematic block diagram of an embodiment of anunderstanding, implementation, operation, or self-analysis module616-619 configured to process the quantity of evaluation metric useindicator 623. The module 616-619 includes a comparator 680, a quantityreference generator 682, a rating generator 681, and a reference scalegenerator 683. As previously discussed, the quantity of evaluationmetric use indicator 623 is based on a count of use of evaluation metricdata (e.g., a count of use of processes, a count of use of policies,etc.).

In an example, the quantity reference generator 682 generates areference use quantity 765 based on evaluation input(s) (e.g.,evaluation viewpoint of disclosed data, discovered data, and/or desireddata; evaluation metric of process, policy, procedure, documentation,certification, automation, and/or other metric; evaluation modality ofsufficiency, effectiveness, quantity of use, appropriate use, and/orconsistency of use; characteristics of the system that include size,capacity, etc., and/or evaluation category of identify, protect, detect,respond, and/or recover).

The comparator 680 compares the quantity of evaluation metric useindicator 623 associated with a particular evaluation perspective (e.g.,understanding, implementation, operation, or self-analysis) with thereference quantity 665 (e.g., an anticipated level of use based on aconventional system or a state-of-art system) to produce a comparisonoutput 766. For example, the comparator compares a count of use ofprocesses (e.g., 12) for the evaluation perspective of understandingwith an understanding reference quantity of use of processes (e.g., 13)to produce a comparison output 766 (e.g., one less use of processes thanexpected). As another example, the comparator compares a list of use ofprocesses with an understanding reference quantity checklist of use ofprocesses to produce a comparison output 766 (e.g., all identified usesof processes in the list are on the checklist). As another example, thecomparator compares a count of use of processes (e.g., 8) for theevaluation perspective of implementation with an implementationreference quantity of use of processes (e.g., 8) to produce a comparisonoutput 766 (e.g., have the expected number of uses of implementationrelated processes).

The reference generator 683 generates a reference scale 626 based on theevaluation input(s). For example, the reference generator 683 generatesa reference scale for processes for a particular evaluation perspective.As another example, the reference generator 683 generates a referencescale for processes regarding implementation for the evaluation categoryof identify. As another example, the reference generator 683 generates areference scale for documentation regarding operation for the evaluationcategory of identify from disclosed data. Further examples of referencescales are provided with reference to FIGS. 119-124 .

The rating generator 681 generates an evaluation rating 627 regardinguse of an evaluation metric-evaluation perspective combination. Based onthe previous example, the compare output 684 indicates that the count ofuse of identified processes within the collection of data was one lessthan the expected use for understanding and indicates that, forimplementation, the quantity of use of processes was as expected. Therating generator 681 maps the compare output 626 (e.g., one less use ofprocesses than expected and as expected) to the reference scale 626(e.g., a bell shaped curve having a scale for one or more of theevaluation metric-evaluation perspective combinations) to produce theevaluation rating 627 for processes based on use and for understanding.

FIG. 118 is a logic diagram of an example of a module of FIG. 117generating an evaluation metric rating 627. The method includes step 767where the module receives one or more evaluation inputs (e.g.,evaluation viewpoint, evaluation modality, evaluation category, systemcharacteristics, and/or evaluation metric). The method continues atsteps 768 and 769. At step 768, the module determines a reference usequantity based on the evaluation input(s). At step 769, the moduledetermines a use reference scale based on the evaluation input(s).

The method further includes step 770 where the module receives aquantity of evaluation metric indication (e.g., a result of a count ofuse of processes, a result of a checklist of use of processes, etc.).The method continues at step 769 where the module produces a compareoutput based on the quantity of evaluation metric indication and thereference use quantity. The method continues at step 772 where themodule generates an evaluation rating for an evaluation metric based onthe compare output and the reference scale.

FIG. 119 is a logic diagram of an example of a module of FIG. 117generating a process use evaluation rating. The method begins at step773 where the module evaluates the quantity of use of processes todetermine whether there is at least one use of a process in thecollection of data. Note that the threshold number in this step could begreater than one. If there are no uses of a process, the methodcontinues at step 774 where the module generates a process use rating of0 (and/or a word rating of “none”).

If there is at least one use of a process, the method continues at step775 where the module determines whether the use of the processes isrepeatable. As a further and/or alternative example, repeatable includesmeans to track uses of processes, there are some tracking variations,the count is not routinely reviewed in an organized manner, and/or thecount is not regulated.

If the use of the processes is not repeatable, the method continues atstep 776 where the module generates a process use rating of 10 (and/or aword rating of “inconsistent”). If, however, the use of processes is atleast repeatable, the method continues at step 774 where the moduledetermines whether the use of the processes is standardized. As afurther and/or alternative example, standardized use includes repeatableplus the count of the processes is regulated.

If the use of the processes is not standardized, the method continues atstep 778 where the module generates a process rating of 20 (and/or aword rating of “repeatable”). If, however, the use of the processes isat least standardized, the method continues at step 779 where the moduledetermines whether the use of the processes is measured. As a furtherand/or alternative example, measured includes standardized plus thereare no appreciable tracking variations.

If the use of the processes is not measured, the method continues atstep 780 where the module generates a process use rating of 30 (and/or aword rating of “standardized”). If, however, the use of the processes isat least measured, the method continues at step 781 where the moduledetermines whether the use of the processes is optimized. As a furtherand/or alternative example, optimized includes measured plus the countis routinely reviewed in an organized manner.

If the use of the processes is not optimized, the method continues atstep 782 where the module generates a process use rating of 40 (and/or aword rating of “measured”). If the use of the processes is optimized,the method continues at step 783 where the module generates a processuse rating of 50 (and/or a word rating of “optimized”). Note that thenumerical rating are example values and could be other values. Furthernote that the number of level of use of process rating may be more orless than the six shown.

FIG. 120 is a logic diagram of an example of a module of FIG. 117generating an evaluation policy use rating. The method begins at step784 where the module determines whether there is at least one use of apolicy in the collection of data. Note that the threshold number in thisstep could be greater than one. If there are no uses of a policy, themethod continues at step 785 where the module generates a policy userating of 0 (and/or a word rating of “none”).

If there is at least one use of a policy, the method continues at step786 where the module determines whether use of the policies is defined.As a further and/or alternative example, defined use of policiesincludes means to track uses of policies, there are some trackingvariations, the count is not routinely reviewed in an organized manner,and/or the count is not regulated.

If the use of the policies is not defined, the method continues at step787 where the module generates a policy use rating of 5 (and/or a wordrating of “informal”). If, however, the use of the policies is at leastdefined, the method continues at step 788 where the module determineswhether use of policies is audited. As a further and/or alternativeexample, audited includes defined plus there are negligible trackingvariations.

If the use of the policies is not audited, the method continues at step789 where the module generates a policy use rating of 10 (and/or a wordrating of “defined”). If, however, the use of the policies is at leastaudited, the method continues at step 790 where the module determineswhether the use of the policies is embedded. As a further and/oralternative example, embedded includes audited plus the count isroutinely reviewed in an organized manner and the count is regulated.

If the use of the policies is not embedded, the method continues at step791 where the module generates a policy use rating of 15 (and/or a wordrating of “audited”). If the use of policies is embedded, the methodcontinues at step 792 where the module generates a policy use rating of20 (and/or a word rating of “embedded”). Note that the numerical ratingare example values and could be other values. Further note that thenumber of level of use of policy rating may be more or less than thefive shown.

FIG. 121 is a logic diagram of an example of a module of FIG. 117generating a documentation use evaluation rating. The method begins atstep 793 where the module determines whether there is at least one useof a document in the collection of data. Note that the threshold numberin this step could be greater than one. If there are no uses of adocument, the method continues at step 794 where the module generates adocumentation use rating of 0 (and/or a word rating of “none”).

If there is at least one use of a document, the method continues at step795 where the module determines whether the use of documents isformalized. As a further and/or alternative example, formalized use ofdocuments includes means for tracking use of documents (e.g., access adocument, create a document, edit a document, etc.), there are sometracking variations, the count is not routinely reviewed in an organizedmanner, and/or the count is not regulated.

If the use of documents is not formalized, the method continues at step796 where the module generates a documentation use rating of 5 (and/or aword rating of “informal”). If, however, the use of documents is atleast formalized, the method continues at step 797 where the moduledetermines whether the use of documents is metric & reporting. As afurther and/or alternative example, metric & reporting includes formalplus there are negligible tracking variations.

If the use of documents is not metric & reporting, the method continuesat step 798 where the module generates a documentation use rating of 10(and/or a word rating of “formal”). If, however, the use of documents isat least metric & reporting, the method continues at step 799 where themodule determines whether the use of documents is improvement. As afurther and/or alternative example, improvement includes metric &reporting plus the count is routinely reviewed in an organized mannerand the count is regulated.

If the use of documents is not improvement, the method continues at step800 where the module generates a documentation use rating of 15 (and/ora word rating of “metric & reporting”). If the use of documents isimprovement, the method continues at step 801 where the module generatesa documentation use rating of 20 (and/or a word rating of“improvement”). Note that the numerical rating are example values andcould be other values. Further note that the number of level of uses ofdocumentation rating may be more or less than the five shown.

FIG. 122 is a logic diagram of an example of a module of FIG. 117generating an automation use evaluation rating. The method begins atstep 802 where the module determines whether there is availableautomation for a particular system aspect, system criteria, systemfeatures, and/or system mode. If use of automation is not available, themethod continues at step 803 where the module generates an automationrating of 10 (and/or a word rating of “unavailable”).

If use of automation is available (e.g., there is automation for one ormore particular system features), the method continues at step 804 wherethe module determines whether there is at least one use of automation inthe data. If not, the method continues at step 805 where the modulegenerates an automation use rating of 0 (and/or a word rating of“none”).

If there is at least one use of automation, the method continues at step806 where the module determines whether there was full use of automationin the data. As a further and/or alternative example, full use ofautomation refers to a count of use of automation is at an expectedlevel.

If the use of automation is not full, the method continues at step 807where the module generates an automation use rating of 5 (and/or a wordrating of “partial”). If, however, the use of automation is full, themethod continues at step 808 where the module generates an automationuse rating of 10 (and/or a word rating of “full”). Note that thenumerical rating are example values and could be other values. Furthernote that the number of level of use of automation may be more or lessthan the four shown.

FIG. 123 is a logic diagram of an example of a module of FIG. 117generating a procedure use evaluation rating. In this example, themodule uses a reference scale that is similar to the reference scales aswas used for the use of policies, but a different reference scale couldbe use. The method begins at step 809 where the module determineswhether there is at least one use of a procedure in the collection ofdata. Note that the threshold number in this step could be greater thanone. If there are no uses of a procedure, the method continues at step810 where the module generates a procedure use rating of 0 (and/or aword rating of “none”).

If there is at least one use of a procedure, the method continues atstep 811 where the module determines whether use of the procedures isdefined. As a further and/or alternative example, defined use ofprocedures includes means to track uses of procedures, there are sometracking variations, the count is not routinely reviewed in an organizedmanner, and/or the count is not regulated.

If the use of the procedures is not defined, the method continues atstep 812 where the module generates a procedure use rating of 5 (and/ora word rating of “informal”). If, however, the use of the procedures isat least defined, the method continues at step 813 where the moduledetermines whether use of procedures is audited. As a further and/oralternative example, audited includes defined plus there are negligibletracking variations.

If the use of the procedures is not audited, the method continues atstep 814 where the module generates a procedure use rating of 10 (and/ora word rating of “defined”). If, however, the use of the procedures isat least audited, the method continues at step 815 where the moduledetermines whether the use of the procedures is embedded. As a furtherand/or alternative example, embedded includes audited plus the count isroutinely reviewed in an organized manner and the count is regulated.

If the use of the procedures is not embedded, the method continues atstep 816 where the module generates a procedure use rating of 15 (and/ora word rating of “audited”). If the use of procedures is embedded, themethod continues at step 817 where the module generates a procedure userating of 20 (and/or a word rating of “embedded”). Note that thenumerical rating are example values and could be other values. Furthernote that the number of level of use of procedure rating may be more orless than the five shown.

FIG. 124 is a logic diagram of an example of a module of FIG. 117generating a certificate use evaluation rating. In this example, themodule uses a reference scale that is similar to the reference scales aswas used for documentation, but a different reference scale could beuse. The method begins at step 818 where the module determines whetherthere is at least one use of a certificate (e.g., obtaining acertificate, verifying a certificate, updating a certificate, etc.) inthe collection of data. Note that the threshold number in this stepcould be greater than one. If there are no uses of a certificate, themethod continues at step 819 where the module generates a certificationuse rating of 0 (and/or a word rating of “none”).

If there is at least one use of a certificate, the method continues atstep 820 where the module determines whether the use of certificates isformalized. As a further and/or alternative example, formalized use ofcertificates includes means for tracking use of certificates, there aresome tracking variations, the count is not routinely reviewed in anorganized manner, and/or the count is not regulated.

If the use of certificates is not formalized, the method continues atstep 821 where the module generates a certification use rating of 5(and/or a word rating of “informal”). If, however, the use ofcertificates is at least formalized, the method continues at step 822where the module determines whether the use of certificates is metric &reporting. As a further and/or alternative example, metric & reportingincludes formal plus there are negligible tracking variations.

If the use of certificates is not metric & reporting, the methodcontinues at step 823 where the module generates a certification userating of 10 (and/or a word rating of “formal”). If, however, the use ofcertificates is at least metric & reporting, the method continues atstep 824 where the module determines whether the use of certificates isimprovement. As a further and/or alternative example, improvementincludes metric & reporting plus the count is routinely reviewed in anorganized manner and the count is regulated.

If the use of certificates is not improvement, the method continues atstep 825 where the module generates a certification use rating of 15(and/or a word rating of “metric & reporting”). If the use ofcertificates is improvement, the method continues at step 826 where themodule generates a certification use rating of 20 (and/or a word ratingof “improvement”). Note that the numerical rating are example values andcould be other values. Further note that the number of level of uses ofcertification rating may be more or less than the five shown.

FIG. 125 is a schematic block diagram of an embodiment of anunderstanding, implementation, operation, or self-analysis 616-619 forprocessing the quantified appropriate use of evaluation metricindication 624. In this embodiment, the module 616-619 includes thereference scale generator 683 and the rating generator 681.

The reference generator 683 generates a reference scale 626 based on oneor more evaluation inputs (e.g., one or more evaluation viewpoints; oneor more evaluation metrics; one or more evaluation modalities; one ormore characteristics of the system; and/or one or more evaluationcategories). For example, the reference scale generator 683 generates areference scale for evaluating appropriate use of processes of: none fora rating of 0; inconsistent for a rating of 10; repeatable for a ratingof 20; standardized for a rating of 30; measured for a rating of 40; andoptimized for rating of 50.

In this example, a level of “none” on the reference scale for theappropriate use of processes corresponds to zero or near zero confidencein the appropriate use of the processes to reliably, repeatedly, and/orcompletely indicate that the system, or portion thereof, fulfills theobjectives of the system, or portion thereof, (e.g., some to all ofguidelines, system requirements, system design, system build, and/orsystem operation). Continuing with this example, a level of“inconsistent” on the reference scale for appropriate use of processescorresponds to low confidence level of appropriate use of the processesto reliably, repeatedly, and/or completely indicate that the system, orportion thereof, fulfills the objectives of the system, or portionthereof. As an example of inconsistent, there are gaps (e.g., missing,incomplete, inaccurate, etc.) in conditions as to when processes are tobe used. As another example of inconsistent, the conditions for use ofone or more processes is inconsistent (e.g., contradicts, produces aninfinite loop, creates a deadlock, etc.) with conditions for use of oneor more other the processes.

Continuing with this example, a level of “repeatable” on the referencescale for the appropriate use of processes corresponds to low to midlevel of confidence of appropriate use of the processes to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof. Asan example of repeatable, the conditions for use processes producerepeatable uses of the processes to fulfill at least some of theobjectives, or portions thereof, but the conditions for use of processesare static (not regularly reviewed, not regularly updated, etc.), theconditions of use have varying degrees of specificity (e.g., some verydetailed, others are vague), the conditions for use are more generic innature than specific to the system, and/or are the conditions for usecreated in a consistent manner.

Continuing with this example, a level of “standardized” on the referencescale for appropriate use of processes corresponds to mid-levelconfidence of the appropriate use of the processes to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof. Asan example of standardized, the conditions for use of the processesproduce repeatable uses of the processes to fulfill at least some of theobjectives, or portions thereof, and the conditions of use are createdin a consistent (e.g., standardized) manner, but conditions of use ofthe processes are static (not regularly reviewed, not regularly updated,etc.), the conditions of use have varying degrees of specificity, and/orthe conditions of use are more generic in nature than specific to thesystem.

Continuing with this example, a level of “measured” on the referencescale for the appropriate use of processes corresponds to mid to highlevel of confidence in the appropriate use of the processes to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof. Asan example of measured, the conditions for use of the processes producerepeatable uses of the processes to fulfill at least some of theobjectives, or portions thereof, the conditions of use of processes arecreated in a consistent manner, the conditions for use have consistentspecificity, and the conditions for use are specific to the system, butthe conditions for use of processes are static (not regularly reviewed,not regularly updated, etc.).

Continuing with this example, a level of “optimized” on the referencescale for appropriate use of processes corresponds to high level ofconfidence in the appropriate use of the processes to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof. Asan example of optimized, the conditions of use of the processes producerepeatable uses of the processes to fulfill at least some of theobjectives, or portions thereof, the conditions of use of the processesare created in a consistent manner, the conditions of use haveconsistent specificity, the conditions of use are specific to thesystem, and the conditions of use are dynamic (regularly reviewed,regularly updated, etc.).

The reference scale generator 683 generates a reference scale forevaluating appropriate use of policies. As an example, the referencescale includes: none for a rating of 0; informal for a rating of 5;defined for a rating of 10; audited for a rating of 15; and embedded fora rating of 20. In this example, a level of “none” on the referencescale for appropriate use of policies corresponds to zero or near zeroconfidence in the appropriate use of the policies to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof.

Continuing with this example, a level of “informal” on the referencescale for appropriate use of policies corresponds to low level ofconfidence of the appropriate use of policies to reliably, repeatedly,and/or completely indicate that the system, or portion thereof, fulfillsthe objectives of the system, or portion thereof. As an example ofinformal, the conditions for use of one or more policies is inconsistent(e.g., contradicts, produces an infinite loop, creates a deadlock, etc.)with conditions for use of one or more other the policies. As anotherexample of informal, there are gaps (e.g., missing, incomplete,inaccurate, etc.) in conditions as to when policies are to be used.

Continuing with this example, a level of “defined” on the referencescale for appropriate use of policies corresponds to low to mid level ofconfidence of appropriate use of the policies to reliably, repeatedly,and/or completely indicate that the system, or portion thereof, fulfillsthe objectives of the system, or portion thereof. As an example ofdefined, the conditions for use policies produce repeatable uses of thepolicies to fulfill at least some of the objectives, or portionsthereof, but the conditions for use of policies are static (notregularly reviewed, not regularly updated, etc.), the conditions of usehave varying degrees of specificity (e.g., some very detailed, othersare vague), the conditions for use are more generic in nature thanspecific to the system, and/or are the conditions for use created in aconsistent manner.

Continuing with this example, a level of “audited” on the referencescale for appropriate use of policies corresponds to mid to high levelof confidence of appropriate use of the policies to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof. Asan example of audited, the conditions for use of the policies producerepeatable uses of the policies to fulfill at least some of theobjectives, or portions thereof, the conditions of use of policies arecreated in a consistent manner, the conditions for use have consistentspecificity, and the conditions for use are specific to the system, butthe conditions for use of policies are static (not regularly reviewed,not regularly updated, etc.).

Continuing with this example, a level of “embedded” on the referencescale for appropriate use of policies corresponds to high level ofconfidence of appropriate use of the policies to reliably, repeatedly,and/or completely indicate that the system, or portion thereof, fulfillsthe objectives of the system, or portion thereof. As an example ofembedded, the conditions of use of the policies produce repeatable usesof the policies to fulfill at least some of the objectives, or portionsthereof, the conditions of use of the policies are created in aconsistent manner, the conditions of use have consistent specificity,the conditions of use are specific to the system, and the conditions ofuse are dynamic (regularly reviewed, regularly updated, etc.).

As another example, the reference scale generator 683 generates areference scale for evaluating appropriate use of documents of: none fora rating of 0; informal for a rating of 5; formal for a rating of 10;metric & reporting for a rating of 15; and improvement for a rating of20. In this example, a level of “none” on the reference scale forappropriate use of documents corresponds to zero or near zero confidenceof appropriate use of documents to reliably, repeatedly, and/orcompletely indicate that the system, or portion thereof, fulfills theobjectives of the system, or portion thereof.

Continuing with this example, a level of “informal” on the referencescale for appropriate use of documents corresponds to low level ofconfidence of appropriate use of the documents to reliably, repeatedly,and/or completely indicate that the system, or portion thereof, fulfillsthe objectives of the system, or portion thereof. As an example ofinformal, there are gaps (e.g., missing, incomplete, inaccurate, etc.)in conditions as to when documents are to be used. As another example ofinconsistent, the conditions for use of one or more documents isinconsistent (e.g., contradicts, produces an infinite loop, creates adeadlock, etc.) with conditions for use of one or more other thedocuments.

Continuing with this example, a level of “formal” on the reference scalefor appropriate use of documents corresponds to low to mid level ofconfidence of appropriate use of documents to reliably, repeatedly,and/or completely indicate that the system, or portion thereof, fulfillsthe objectives of the system, or portion thereof. As an example ofdefined, the conditions for use of documents produce repeatable uses ofthe processes to fulfill at least some of the objectives, or portionsthereof, but the conditions for use of documents are static (notregularly reviewed, not regularly updated, etc.), the conditions of usehave varying degrees of specificity (e.g., some very detailed, othersare vague), the conditions for use are more generic in nature thanspecific to the system, and/or are the conditions for use created in aconsistent manner.

Continuing with this example, a level of “metric & reporting” on thereference scale for appropriate use of documents corresponds to mid tohigh level of confidence of appropriate use of the documents toreliably, repeatedly, and/or completely indicate that the system, orportion thereof, fulfills the objectives of the system, or portionthereof. As an example of metric & reporting, the conditions for use ofthe documents produce repeatable uses of the documents to fulfill atleast some of the objectives, or portions thereof, the conditions of useof documents are created in a consistent manner, the conditions for usehave consistent specificity, and the conditions for use are specific tothe system, but the conditions for use of documents are static (notregularly reviewed, not regularly updated, etc.).

Continuing with this example, a level of “improvement” on the referencescale for appropriate use of documents corresponds to high level ofconfidence of appropriate use of the documents to reliably, repeatedly,and/or completely indicate that the system, or portion thereof, fulfillsthe objectives of the system, or portion thereof. As an example ofimprovement, the conditions of use of the documents produce repeatableuses of the documents to fulfill at least some of the objectives, orportions thereof, the conditions of use of the documents are created ina consistent manner, the conditions of use have consistent specificity,the conditions of use are specific to the system, and the conditions ofuse are dynamic (regularly reviewed, regularly updated, etc.).

As another example, the reference scale generator 683 generates areference scale for evaluating appropriate use of automation of:unavailable for a rating of 10; none for a rating of 0; partial for arating of 5; and full for a rating of 10. In this example, a level of“unavailable” for appropriate use of automation corresponds toautomation for a particular incident (e.g., automation of a feature ofthe system) is not available. Continuing with this example, a level of“none” on the reference scale for appropriate use of automationcorresponds to zero or near zero confidence in appropriate use ofautomation within the system, or portion thereof.

Continuing with this example, a level of “partial” on the referencescale for appropriate use of automation corresponds to mid-levelconfidence of appropriate use of automation within the system, orportion thereof. As an example of partial, the conditions for use ofautomation produce repeatable uses of automation, the conditions of useare created in a consistent (e.g., standardized) manner, but conditionsof use of the automation are static (not regularly reviewed, notregularly updated, etc.), the conditions of use have varying degrees ofspecificity, and/or the conditions of use are more generic in naturethan specific to the system.

Continuing with this example, a level of “full” on the reference scalefor appropriate use of automation corresponds to high level ofconfidence in appropriate use of automation within the system, orportion thereof. As an example of full, the conditions of use ofautomation produce repeatable uses of automation, the conditions of useof automation are created in a consistent manner, the conditions of usehave consistent specificity, the conditions of use are specific to thesystem, and the conditions of use are dynamic (regularly reviewed,regularly updated, etc.).

The reference scale generator 683 generates a reference scale forevaluating appropriate use of procedures of: none for a rating of 0;informal for a rating of 5; defined for a rating of 10; audited for arating of 15; and embedded for a rating of 20. The reference scalegenerator 683 also generates a reference scale for evaluatingappropriate use of certificates of: none for a rating of 0; informal fora rating of 5; forma for a rating of 10; metric & reporting for a ratingof 15; and improvement for a rating of 20.

The rating generator 681 generates the evaluation rating 627 for thequantified appropriate use (e.g., not used when not supposed to be used)of the evaluation metric indicator 624 based on the reference scale 626.For each of the evaluation metrics, the rating generator 681 maps thequantified appropriate use of the evaluation metric to the referencescale 626. As an example, the rating generator 681 maps the quantifiedappropriate use of processes to the process reference scale 626. In thisexample, the quantified appropriate use of processes includes anindication for the conditions of use of the processes showing repeatableuses of the processes to fulfill at least some of the objectives, orportions thereof, an indication that the conditions of use of theprocesses are created in a consistent manner, an indication that theconditions of use have consistent specificity, an indication that theconditions of use are specific to the system, and/or an indication thatthe conditions of use are dynamic (regularly reviewed, regularlyupdated, etc.). Additional examples are provided with reference to FIGS.126-131 .

FIG. 126 is a logic diagram of an example of a module of FIG. 125generating an evaluation metric rating. The method begins at step 827where the module evaluates the quantified appropriate use of processesto determine whether there is at least one appropriate use of a processin the collection of data. Note that the threshold number in this stepcould be greater than one. If there are no appropriate uses of aprocess, the method continues at step 828 where the module generates anappropriate use process rating of 0 (and/or a word rating of “none”).

If there is at least one appropriate use of a process, the methodcontinues at step 829 where the module determines whether the conditionsof use of processes are repeatable. As a further and/or alternativeexample, repeatable includes conditions of use of processes produceconsistent results, condition detail variations from process to process,the conditions of use are not routinely reviewed in an organized manner,and/or the conditions of use are not regulated.

If the conditions of use of the processes are not repeatable, the methodcontinues at step 830 where the module generates a process rating of 10(and/or a word rating of “inconsistent”). If, however, the conditions ofuse of processes are at least repeatable, the method continues at step831 where the module determines whether the conditions of use of theprocesses is standardized. As a further and/or alternative example,standardized includes repeatable plus there are no appreciablevariations in detail of conditions of use of the processes from processto process, and/or the conditions of use of the processes are regulated.

If the conditions of use of the processes is not standardized, themethod continues at step 832 where the module generates a process ratingof 20 (and/or a word rating of “repeatable”). If, however, theconditions of use of the processes are at least standardized, the methodcontinues at step 833 where the module determines whether the conditionsof use of the processes is measured. As a further and/or alternativeexample, measured includes standardized plus precise, exact, and/orconditions of use calculated to specific needs, concerns, and/orfunctioning of the system.

If the conditions of use of the processes is not measured, the methodcontinues at step 834 where the module generates a process rating of 30(and/or a word rating of “standardized”). If, however, the conditions ofuse of the processes is at least measured, the method continues at step835 where the module determines whether the conditions of use of theprocesses is optimized. As a further and/or alternative example,optimized includes measured plus conditions of use of the processes areup-to-date and/or improvement of the conditions of use of the process isassessed on a regular basis as part of system protocols.

If the conditions of use of the processes is not optimized, the methodcontinues at step 836 where the module generates a process rating of 40(and/or a word rating of “measured”). If the conditions of use of theprocesses is optimized, the method continues at step 837 where themodule generates a process rating of 50 (and/or a word rating of“optimized”). Note that the numerical rating are example values andcould be other values. Further note that the number of level of processrating may be more or less than the six shown.

FIG. 127 is a logic diagram of an example of a module of FIG. 125generating an appropriate use of policy evaluation rating. The methodbegins at step 838 where the module determines whether there is at leastone appropriate use of a policy in the collection of data. Note that thethreshold number in this step could be greater than one. If there are noappropriate uses of a policy, the method continues at step 839 where themodule generates an appropriate use of policy rating of 0 (and/or a wordrating of “none”).

If there is at least one appropriate use of a policy, the methodcontinues at step 840 where the module determines whether theappropriate use of the policies is defined. As a further and/oralternative example, defined appropriate use of policies includes meansto track conditions of use of policies, there are some trackingvariations, the conditions of use are not routinely reviewed in anorganized manner, and/or the conditions of use are not regulated.

If the appropriate use of the policies is not defined, the methodcontinues at step 841 where the module generates an appropriate use ofpolicy rating of 5 (and/or a word rating of “informal”). If, however,the appropriate use of the policies is at least defined, the methodcontinues at step 842 where the module determines whether appropriateuse of policies is audited. As a further and/or alternative example,audited includes defined plus there are negligible tracking variations.

If the appropriate use of the policies is not audited, the methodcontinues at step 843 where the module generates an appropriate use ofpolicy rating of 10 (and/or a word rating of “defined”). If, however,the appropriate use of the policies is at least audited, the methodcontinues at step 844 where the module determines whether theappropriate use of the policies is embedded. As a further and/oralternative example, embedded includes audited plus the conditions ofuse are routinely reviewed in an organized manner and the conditions ofuse are regulated.

If the appropriate use of the policies is not embedded, the methodcontinues at step 845 where the module generates an appropriate use ofpolicy rating of 15 (and/or a word rating of “audited”). If theappropriate use of policies is embedded, the method continues at step846 where the module generates an appropriate use of policy rating of 20(and/or a word rating of “embedded”). Note that the numerical rating areexample values and could be other values. Further note that the numberof level of appropriate use of policy rating may be more or less thanthe five shown.

FIG. 128 is a logic diagram of an example of a module of FIG. 125generating an appropriate use documentation evaluation rating. Themethod begins at step 847 where the module determines whether there isat least one appropriate use of a document in the collection of data.Note that the threshold number in this step could be greater than one.If there are no appropriate uses of a document, the method continues atstep 848 where the module generates an appropriate use of documentationrating of 0 (and/or a word rating of “none”).

If there is at least one appropriate use of a document, the methodcontinues at step 849 where the module determines whether theappropriate use of documents is formalized. As a further and/oralternative example, formalized appropriate use of documents includesmeans for tracking appropriate use of documents, there are some trackingvariations, the conditions of use is not routinely reviewed in anorganized manner, and/or the conditions of use is not regulated.

If the appropriate use of documents is not formalized, the methodcontinues at step 850 where the module generates an appropriate use ofdocumentation rating of 5 (and/or a word rating of “informal”). If,however, the appropriate use of documents is at least formalized, themethod continues at step 851 where the module determines whether theappropriate use of documents is metric & reporting. As a further and/oralternative example, metric & reporting includes formal plus there arenegligible tracking variations.

If the appropriate use of documents is not metric & reporting, themethod continues at step 852 where the module generates an appropriateuse of documentation rating of 10 (and/or a word rating of “formal”).If, however, the appropriate use of documents is at least metric &reporting, the method continues at step 853 where the module determineswhether the appropriate use of documents is improvement. As a furtherand/or alternative example, improvement includes metric & reporting plusthe conditions of use are routinely reviewed in an organized manner andthe conditions of use are regulated.

If the appropriate use of documents is not improvement, the methodcontinues at step 854 where the module generates an appropriate use ofdocumentation rating of 15 (and/or a word rating of “metric &reporting”). If the appropriate use of documents is improvement, themethod continues at step 855 where the module generates an appropriateuse of documentation rating of 20 (and/or a word rating of“improvement”). Note that the numerical rating are example values andcould be other values. Further note that the number of level ofappropriate use of documentation rating may be more or less than thefive shown.

FIG. 129 is a logic diagram of an example of a module of FIG. 125generating an appropriate use of procedure evaluation rating. The methodbegins at step 856 where the module determines whether there is at leastone appropriate use of a procedure in the collection of data. Note thatthe threshold number in this step could be greater than one. If thereare no appropriate uses of a procedure, the method continues at step 857where the module generates an appropriate use of procedure rating of 0(and/or a word rating of “none”).

If there is at least one appropriate use of a procedure, the methodcontinues at step 858 where the module determines whether theappropriate use of the procedures is defined. As a further and/oralternative example, defined appropriate use of procedures includesmeans to track conditions of use of procedures, there are some trackingvariations, the conditions of use are not routinely reviewed in anorganized manner, and/or the conditions of use are not regulated.

If the appropriate use of the procedures is not defined, the methodcontinues at step 859 where the module generates an appropriate use ofprocedure rating of 5 (and/or a word rating of “informal”). If, however,the appropriate use of the procedures is at least defined, the methodcontinues at step 860 where the module determines whether appropriateuse of procedures is audited. As a further and/or alternative example,audited includes defined plus there are negligible tracking variations.

If the appropriate use of the procedures is not audited, the methodcontinues at step 861 where the module generates an appropriate use ofprocedure rating of 10 (and/or a word rating of “defined”). If, however,the appropriate use of the procedures is at least audited, the methodcontinues at step 862 where the module determines whether theappropriate use of the procedures is embedded. As a further and/oralternative example, embedded includes audited plus the conditions ofuse are routinely reviewed in an organized manner and the conditions ofuse are regulated.

If the appropriate use of the procedures is not embedded, the methodcontinues at step 863 where the module generates an appropriate use ofprocedure rating of 15 (and/or a word rating of “audited”). If theappropriate use of procedures is embedded, the method continues at step864 where the module generates an appropriate use of procedure rating of20 (and/or a word rating of “embedded”). Note that the numerical ratingare example values and could be other values. Further note that thenumber of level of appropriate use of procedure rating may be more orless than the five shown.

FIG. 130 is a logic diagram of an example of a module of FIG. 125generating an appropriate use certification evaluation rating. Themethod begins at step 865 where the module determines whether there isat least one appropriate use of a certificate in the collection of data.Note that the threshold number in this step could be greater than one.If there are no appropriate uses of a certificate, the method continuesat step 866 where the module generates an appropriate use ofcertification rating of 0 (and/or a word rating of “none”).

If there is at least one appropriate use of a certificate, the methodcontinues at step 867 where the module determines whether theappropriate use of certificates is formalized. As a further and/oralternative example, formalized appropriate use of certificates includesmeans for tracking appropriate use of certificates, there are sometracking variations, the conditions of use is not routinely reviewed inan organized manner, and/or the conditions of use is not regulated.

If the appropriate use of certificates is not formalized, the methodcontinues at step 868 where the module generates an appropriate use ofcertification rating of 5 (and/or a word rating of “informal”). If,however, the appropriate use of certificates is at least formalized, themethod continues at step 869 where the module determines whether theappropriate use of certificates is metric & reporting. As a furtherand/or alternative example, metric & reporting includes formal plusthere are negligible tracking variations.

If the appropriate use of certificates is not metric & reporting, themethod continues at step 870 where the module generates an appropriateuse of certification rating of 10 (and/or a word rating of “formal”).If, however, the appropriate use of certificates is at least metric &reporting, the method continues at step 871 where the module determineswhether the appropriate use of certificates is improvement. As a furtherand/or alternative example, improvement includes metric & reporting plusthe conditions of use are routinely reviewed in an organized manner andthe conditions of use are regulated.

If the appropriate use of certificates is not improvement, the methodcontinues at step 872 where the module generates an appropriate use ofcertification rating of 15 (and/or a word rating of “metric &reporting”). If the appropriate use of certificates is improvement, themethod continues at step 873 where the module generates an appropriateuse of certification rating of 20 (and/or a word rating of“improvement”). Note that the numerical rating are example values andcould be other values. Further note that the number of level ofappropriate use of certification rating may be more or less than thefive shown.

FIG. 131 is a logic diagram of an example of a module of FIG. 125generating an appropriate use of automation evaluation rating. Themethod begins at step 874 where the module determines whether there isavailable automation for a particular system aspect, system criteria,system features, and/or system mode. If use of automation is notavailable, the method continues at step 875 where the module generatesan automation rating of 10 (and/or a word rating of “unavailable”).

If use of automation is available (e.g., there is automation for one ormore particular system features), the method continues at step 876 wherethe module determines whether there is at least one appropriate use ofautomation in the data. If not, the method continues at step 877 wherethe module generates an appropriate use of automation rating of 0(and/or a word rating of “none”).

If there is at least one appropriate use of automation, the methodcontinues at step 878 where the module determines whether there was fullappropriate use of automation in the data. As a further and/oralternative example, full appropriate use of automation refers to theconditions of use of automation is at an expected level.

If the appropriate use of automation is not full, the method continuesat step 879 where the module generates an appropriate use of automationrating of 5 (and/or a word rating of “partial”). If, however, theappropriate use of automation is full, the method continues at step 880where the module generates an appropriate use of automation rating of 10(and/or a word rating of “full”). Note that the numerical rating areexample values and could be other values. Further note that the numberof level of use of automation may be more or less than the four shown.

FIG. 132 is a schematic block diagram of an embodiment of anunderstanding, implementation, operation, or self-analysis 616-619 forprocessing the quantified consistency of use of evaluation metricindication 624 (e.g., inconsistency equates to not being used when itshould have been). In this embodiment, the module 616-619 includes thereference scale generator 683 and the rating generator 681.

The reference generator 683 generates a reference scale 626 based on oneor more evaluation inputs (e.g., one or more evaluation viewpoints; oneor more evaluation metrics; one or more evaluation modalities; one ormore characteristics of the system; and/or one or more evaluationcategories). For example, the reference scale generator 683 generates areference scale for evaluating consistency of use of processes of: nonefor a rating of 0; inconsistent for a rating of 10; repeatable for arating of 20; standardized for a rating of 30; measured for a rating of40; and optimized for rating of 50.

In this example, a level of “none” on the reference scale for theconsistency of use of processes corresponds to zero or near zeroconfidence in the consistency of use of the processes to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof,(e.g., some to all of guidelines, system requirements, system design,system build, and/or system operation). Continuing with this example, alevel of “inconsistent” on the reference scale for consistency of use ofprocesses corresponds to low confidence level of consistency of use ofthe processes to reliably, repeatedly, and/or completely indicate thatthe system, or portion thereof, fulfills the objectives of the system,or portion thereof. As an example of inconsistent, there are gaps (e.g.,missing, incomplete, inaccurate, etc.) in situations as to whenprocesses are to be used. As another example of inconsistent, thesituations for use of one or more processes is inconsistent (e.g.,contradicts, produces an infinite loop, creates a deadlock, etc.) withsituations for use of one or more other the processes.

Continuing with this example, a level of “repeatable” on the referencescale for the consistency of use of processes corresponds to low to midlevel of confidence of consistency of use of the processes to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof. Asan example of repeatable, the situations for use processes producerepeatable uses of the processes to fulfill at least some of theobjectives, or portions thereof, but the situations for use of processesare static (not regularly reviewed, not regularly updated, etc.), thesituations of use have varying degrees of specificity (e.g., some verydetailed, others are vague), the situations for use are more generic innature than specific to the system, and/or are the situations for usecreated in a consistent manner.

Continuing with this example, a level of “standardized” on the referencescale for consistency of use of processes corresponds to mid-levelconfidence of the consistency of use of the processes to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof. Asan example of standardized, the situations for use of the processesproduce repeatable uses of the processes to fulfill at least some of theobjectives, or portions thereof, and the situations of use are createdin a consistent (e. g., standardized) manner, but situations of use ofthe processes are static (not regularly reviewed, not regularly updated,etc.), the situations of use have varying degrees of specificity, and/orthe situations of use are more generic in nature than specific to thesystem.

Continuing with this example, a level of “measured” on the referencescale for the consistency of use of processes corresponds to mid to highlevel of confidence in the consistency of use of the processes toreliably, repeatedly, and/or completely indicate that the system, orportion thereof, fulfills the objectives of the system, or portionthereof. As an example of measured, the situations for use of theprocesses produce repeatable uses of the processes to fulfill at leastsome of the objectives, or portions thereof, the situations of use ofprocesses are created in a consistent manner, the situations for usehave consistent specificity, and the situations for use are specific tothe system, but the situations for use of processes are static (notregularly reviewed, not regularly updated, etc.).

Continuing with this example, a level of “optimized” on the referencescale for consistency of use of processes corresponds to high level ofconfidence in the consistency of use of the processes to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof. Asan example of optimized, the situations of use of the processes producerepeatable uses of the processes to fulfill at least some of theobjectives, or portions thereof, the situations of use of the processesare created in a consistent manner, the situations of use haveconsistent specificity, the situations of use are specific to thesystem, and the situations of use are dynamic (regularly reviewed,regularly updated, etc.).

The reference scale generator 683 generates a reference scale forevaluating consistency of use of policies. As an example, the referencescale includes: none for a rating of 0; informal for a rating of 5;defined for a rating of 10; audited for a rating of 15; and embedded fora rating of 20. In this example, a level of “none” on the referencescale for consistency of use of policies corresponds to zero or nearzero confidence in the consistency of use of the policies to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof.

Continuing with this example, a level of “informal” on the referencescale for consistency of use of policies corresponds to low level ofconfidence of the consistency of use of policies to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof. Asan example of informal, the situations for use of one or more policiesis inconsistent (e.g., contradicts, produces an infinite loop, creates adeadlock, etc.) with situations for use of one or more other thepolicies. As another example of informal, there are gaps (e.g., missing,incomplete, inaccurate, etc.) in situations as to when policies are tobe used.

Continuing with this example, a level of “defined” on the referencescale for consistency of use of policies corresponds to low to mid levelof confidence of consistency of use of the policies to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof. Asan example of defined, the situations for use policies producerepeatable uses of the policies to fulfill at least some of theobjectives, or portions thereof, but the situations for use of policiesare static (not regularly reviewed, not regularly updated, etc.), thesituations of use have varying degrees of specificity (e.g., some verydetailed, others are vague), the situations for use are more generic innature than specific to the system, and/or are the situations for usecreated in a consistent manner.

Continuing with this example, a level of “audited” on the referencescale for consistency of use of policies corresponds to mid to highlevel of confidence of consistency of use of the policies to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof. Asan example of audited, the situations for use of the policies producerepeatable uses of the policies to fulfill at least some of theobjectives, or portions thereof, the situations of use of policies arecreated in a consistent manner, the situations for use have consistentspecificity, and the situations for use are specific to the system, butthe situations for use of policies are static (not regularly reviewed,not regularly updated, etc.).

Continuing with this example, a level of “embedded” on the referencescale for consistency of use of policies corresponds to high level ofconfidence of consistency of use of the policies to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof. Asan example of embedded, the situations of use of the policies producerepeatable uses of the policies to fulfill at least some of theobjectives, or portions thereof, the situations of use of the policiesare created in a consistent manner, the situations of use haveconsistent specificity, the situations of use are specific to thesystem, and the situations of use are dynamic (regularly reviewed,regularly updated, etc.).

As another example, the reference scale generator 683 generates areference scale for evaluating consistency of use of documents of: nonefor a rating of 0; informal for a rating of 5; formal for a rating of10; metric & reporting for a rating of 15; and improvement for a ratingof 20. In this example, a level of “none” on the reference scale forconsistency of use of documents corresponds to zero or near zeroconfidence of consistency of use of documents to reliably, repeatedly,and/or completely indicate that the system, or portion thereof, fulfillsthe objectives of the system, or portion thereof.

Continuing with this example, a level of “informal” on the referencescale for consistency of use of documents corresponds to low level ofconfidence of consistency of use of the documents to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof. Asan example of informal, there are gaps (e.g., missing, incomplete,inaccurate, etc.) in situations as to when documents are to be used. Asanother example of inconsistent, the situations for use of one or moredocuments is inconsistent (e.g., contradicts, produces an infinite loop,creates a deadlock, etc.) with situations for use of one or more otherthe documents.

Continuing with this example, a level of “formal” on the reference scalefor consistency of use of documents corresponds to low to mid level ofconfidence of consistency of use of documents to reliably, repeatedly,and/or completely indicate that the system, or portion thereof, fulfillsthe objectives of the system, or portion thereof. As an example ofdefined, the situations for use of documents produce repeatable uses ofthe processes to fulfill at least some of the objectives, or portionsthereof, but the situations for use of documents are static (notregularly reviewed, not regularly updated, etc.), the situations of usehave varying degrees of specificity (e.g., some very detailed, othersare vague), the situations for use are more generic in nature thanspecific to the system, and/or are the situations for use created in aconsistent manner.

Continuing with this example, a level of “metric & reporting” on thereference scale for consistency of use of documents corresponds to midto high level of confidence of consistency of use of the documents toreliably, repeatedly, and/or completely indicate that the system, orportion thereof, fulfills the objectives of the system, or portionthereof. As an example of metric & reporting, the situations for use ofthe documents produce repeatable uses of the documents to fulfill atleast some of the objectives, or portions thereof, the situations of useof documents are created in a consistent manner, the situations for usehave consistent specificity, and the situations for use are specific tothe system, but the situations for use of documents are static (notregularly reviewed, not regularly updated, etc.).

Continuing with this example, a level of “improvement” on the referencescale for consistency of use of documents corresponds to high level ofconfidence of consistency of use of the documents to reliably,repeatedly, and/or completely indicate that the system, or portionthereof, fulfills the objectives of the system, or portion thereof. Asan example of improvement, the situations of use of the documentsproduce repeatable uses of the documents to fulfill at least some of theobjectives, or portions thereof, the situations of use of the documentsare created in a consistent manner, the situations of use haveconsistent specificity, the situations of use are specific to thesystem, and the situations of use are dynamic (regularly reviewed,regularly updated, etc.).

As another example, the reference scale generator 683 generates areference scale for evaluating consistency of use of automation of:unavailable for a rating of 10; none for a rating of 0; partial for arating of 5; and full for a rating of 10. In this example, a level of“unavailable” for consistency of use of automation corresponds toautomation for a particular incident (e.g., automation of a feature ofthe system) is not available. Continuing with this example, a level of“none” on the reference scale for consistency of use of automationcorresponds to zero or near zero confidence in consistency of use ofautomation within the system, or portion thereof.

Continuing with this example, a level of “partial” on the referencescale for consistency of use of automation corresponds to mid-levelconfidence of consistency of use of automation within the system, orportion thereof. As an example of partial, the situations for use ofautomation produce repeatable uses of automation, the situations of useare created in a consistent (e g, standardized) manner, but situationsof use of the automation are static (not regularly reviewed, notregularly updated, etc.), the situations of use have varying degrees ofspecificity, and/or the situations of use are more generic in naturethan specific to the system.

Continuing with this example, a level of “full” on the reference scalefor consistency of use of automation corresponds to high level ofconfidence in consistency of use of automation within the system, orportion thereof. As an example of full, the situations of use ofautomation produce repeatable uses of automation, the situations of useof automation are created in a consistent manner, the situations of usehave consistent specificity, the situations of use are specific to thesystem, and the situations of use are dynamic (regularly reviewed,regularly updated, etc.).

The reference scale generator 683 generates a reference scale forevaluating consistency of use of procedures of: none for a rating of 0;informal for a rating of 5; defined for a rating of 10; audited for arating of 15; and embedded for a rating of 20. The reference scalegenerator 683 also generates a reference scale for evaluatingconsistency of use of certificates of: none for a rating of 0; informalfor a rating of 5; forma for a rating of 10; metric & reporting for arating of 15; and improvement for a rating of 20.

The rating generator 681 generates the evaluation rating 627 for thequantified consistency of use (e.g., not used when not supposed to beused) of the evaluation metric indicator 624 based on the referencescale 626. For each of the evaluation metrics, the rating generator 681maps the quantified consistency of use of the evaluation metric to thereference scale 626. As an example, the rating generator 681 maps thequantified consistency of use of processes to the process referencescale 626. In this example, the quantified consistency of use ofprocesses includes an indication for the situations of use of theprocesses showing repeatable uses of the processes to fulfill at leastsome of the objectives, or portions thereof, an indication that thesituations of use of the processes are created in a consistent manner,an indication that the situations of use have consistent specificity, anindication that the situations of use are specific to the system, and/oran indication that the situations of use are dynamic (regularlyreviewed, regularly updated, etc.). Additional examples are providedwith reference to FIGS. 126-131 .

FIG. 133 is a logic diagram of an example of a module of FIG. 132generating an evaluation metric rating. The method begins at step 881where the module evaluates the quantified consistency of use ofprocesses to determine whether there is at least one consistency of useof a process in the collection of data. Note that the threshold numberin this step could be greater than one. If there are no consistency ofuses of a process, the method continues at step 882 where the modulegenerates a consistency of use process rating of 0 (and/or a word ratingof “none”).

If there is at least one consistency of use of a process, the methodcontinues at step 883 where the module determines whether the situationsof use of processes are repeatable. As a further and/or alternativeexample, repeatable includes situations of use of processes produceconsistent results, situation detail variations from process to process,the situations of use are not routinely reviewed in an organized manner,and/or the situations of use are not regulated.

If the situations of use of the processes are not repeatable, the methodcontinues at step 884 where the module generates a process rating of 10(and/or a word rating of “inconsistent”). If, however, the situations ofuse of processes are at least repeatable, the method continues at step885 where the module determines whether the situations of use of theprocesses is standardized. As a further and/or alternative example,standardized includes repeatable plus there are no appreciablevariations in detail of situations of use of the processes from processto process, and/or the situations of use of the processes are regulated.

If the situations of use of the processes is not standardized, themethod continues at step 886 where the module generates a process ratingof 20 (and/or a word rating of “repeatable”). If, however, thesituations of use of the processes are at least standardized, the methodcontinues at step 887 where the module determines whether the situationsof use of the processes is measured. As a further and/or alternativeexample, measured includes standardized plus precise, exact, and/orsituations of use calculated to specific needs, concerns, and/orfunctioning of the system.

If the situations of use of the processes is not measured, the methodcontinues at step 888 where the module generates a process rating of 30(and/or a word rating of “standardized”). If, however, the situations ofuse of the processes is at least measured, the method continues at step889 where the module determines whether the situations of use of theprocesses is optimized. As a further and/or alternative example,optimized includes measured plus situations of use of the processes areup-to-date and/or improvement of the situations of use of the process isassessed on a regular basis as part of system protocols.

If the situations of use of the processes is not optimized, the methodcontinues at step 890 where the module generates a process rating of 40(and/or a word rating of “measured”). If the situations of use of theprocesses is optimized, the method continues at step 891 where themodule generates a process rating of 50 (and/or a word rating of“optimized”). Note that the numerical rating are example values andcould be other values. Further note that the number of level of processrating may be more or less than the six shown.

FIG. 134 is a logic diagram of an example of a module of FIG. 132generating a consistency of use of policy evaluation rating. The methodbegins at step 892 where the module determines whether there is at leastone consistency of use of a policy in the collection of data. Note thatthe threshold number in this step could be greater than one. If thereare no consistency of uses of a policy, the method continues at step 893where the module generates a consistency of use of policy rating of 0(and/or a word rating of “none”).

If there is at least one consistency of use of a policy, the methodcontinues at step 894 where the module determines whether theconsistency of use of the policies is defined. As a further and/oralternative example, defined consistency of use of policies includesmeans to track situations of use of policies, there are some trackingvariations, the situations of use are not routinely reviewed in anorganized manner, and/or the situations of use are not regulated.

If the consistency of use of the policies is not defined, the methodcontinues at step 895 where the module generates a consistency of use ofpolicy rating of 5 (and/or a word rating of “informal”). If, however,the consistency of use of the policies is at least defined, the methodcontinues at step 896 where the module determines whether consistency ofuse of policies is audited. As a further and/or alternative example,audited includes defined plus there are negligible tracking variations.

If the consistency of use of the policies is not audited, the methodcontinues at step 897 where the module generates a consistency of use ofpolicy rating of 10 (and/or a word rating of “defined”). If, however,the consistency of use of the policies is at least audited, the methodcontinues at step 898 where the module determines whether theconsistency of use of the policies is embedded. As a further and/oralternative example, embedded includes audited plus the situations ofuse are routinely reviewed in an organized manner and the situations ofuse are regulated.

If the consistency of use of the policies is not embedded, the methodcontinues at step 899 where the module generates a consistency of use ofpolicy rating of 15 (and/or a word rating of “audited”). If theconsistency of use of policies is embedded, the method continues at step900 where the module generates a consistency of use of policy rating of20 (and/or a word rating of “embedded”). Note that the numerical ratingare example values and could be other values. Further note that thenumber of level of consistency of use of policy rating may be more orless than the five shown.

FIG. 135 is a logic diagram of an example of a module of FIG. 132generating a consistency of use documentation evaluation rating. Themethod begins at step 901 where the module determines whether there isat least one consistency of use of a document in the collection of data.Note that the threshold number in this step could be greater than one.If there are no consistency of uses of a document, the method continuesat step 902 where the module generates a consistency of use ofdocumentation rating of 0 (and/or a word rating of “none”).

If there is at least one consistency of use of a document, the methodcontinues at step 903 where the module determines whether theconsistency of use of documents is formalized. As a further and/oralternative example, formalized consistency of use of documents includesmeans for tracking consistency of use of documents, there are sometracking variations, the situations of use is not routinely reviewed inan organized manner, and/or the situations of use is not regulated.

If the consistency of use of documents is not formalized, the methodcontinues at step 904 where the module generates a consistency of use ofdocumentation rating of 5 (and/or a word rating of “informal”). If,however, the consistency of use of documents is at least formalized, themethod continues at step 905 where the module determines whether theconsistency of use of documents is metric & reporting. As a furtherand/or alternative example, metric & reporting includes formal plusthere are negligible tracking variations.

If the consistency of use of documents is not metric & reporting, themethod continues at step 906 where the module generates a consistency ofuse of documentation rating of 10 (and/or a word rating of “formal”).If, however, the consistency of use of documents is at least metric &reporting, the method continues at step 907 where the module determineswhether the consistency of use of documents is improvement. As a furtherand/or alternative example, improvement includes metric & reporting plusthe situations of use are routinely reviewed in an organized manner andthe situations of use are regulated.

If the consistency of use of documents is not improvement, the methodcontinues at step 908 where the module generates a consistency of use ofdocumentation rating of 15 (and/or a word rating of “metric &reporting”). If the consistency of use of documents is improvement, themethod continues at step 909 where the module generates a consistency ofuse of documentation rating of 20 (and/or a word rating of“improvement”). Note that the numerical rating are example values andcould be other values. Further note that the number of level ofconsistency of use of documentation rating may be more or less than thefive shown.

FIG. 136 is a logic diagram of an example of a module of FIG. 132generating a consistency of use of procedure evaluation rating. Themethod begins at step 910 where the module determines whether there isat least one consistency of use of a procedure in the collection ofdata. Note that the threshold number in this step could be greater thanone. If there are no consistency of uses of a procedure, the methodcontinues at step 911 where the module generates a consistency of use ofprocedure rating of 0 (and/or a word rating of “none”).

If there is at least one consistency of use of a procedure, the methodcontinues at step 912 where the module determines whether theconsistency of use of the procedures is defined. As a further and/oralternative example, defined consistency of use of procedures includesmeans to track situations of use of procedures, there are some trackingvariations, the situations of use are not routinely reviewed in anorganized manner, and/or the situations of use are not regulated.

If the consistency of use of the procedures is not defined, the methodcontinues at step 913 where the module generates a consistency of use ofprocedure rating of 5 (and/or a word rating of “informal”). If, however,the consistency of use of the procedures is at least defined, the methodcontinues at step 914 where the module determines whether consistency ofuse of procedures is audited. As a further and/or alternative example,audited includes defined plus there are negligible tracking variations.

If the consistency of use of the procedures is not audited, the methodcontinues at step 915 where the module generates a consistency of use ofprocedure rating of 10 (and/or a word rating of “defined”). If, however,the consistency of use of the procedures is at least audited, the methodcontinues at step 916 where the module determines whether theconsistency of use of the procedures is embedded. As a further and/oralternative example, embedded includes audited plus the situations ofuse are routinely reviewed in an organized manner and the situations ofuse are regulated.

If the consistency of use of the procedures is not embedded, the methodcontinues at step 917 where the module generates a consistency of use ofprocedure rating of 15 (and/or a word rating of “audited”). If theconsistency of use of procedures is embedded, the method continues atstep 918 where the module generates a consistency of use of procedurerating of 20 (and/or a word rating of “embedded”). Note that thenumerical rating are example values and could be other values. Furthernote that the number of level of consistency of use of procedure ratingmay be more or less than the five shown.

FIG. 137 is a logic diagram of an example of a module of FIG. 132generating a consistency of use certification evaluation rating. Themethod begins at step 919 where the module determines whether there isat least one consistency of use of a certificate in the collection ofdata. Note that the threshold number in this step could be greater thanone. If there are no consistency of uses of a certificate, the methodcontinues at step 920 where the module generates a consistency of use ofcertification rating of 0 (and/or a word rating of “none”).

If there is at least one consistency of use of a certificate, the methodcontinues at step 921 where the module determines whether theconsistency of use of certificates is formalized. As a further and/oralternative example, formalized consistency of use of certificatesincludes means for tracking consistency of use of certificates, thereare some tracking variations, the situations of use is not routinelyreviewed in an organized manner, and/or the situations of use is notregulated.

If the consistency of use of certificates is not formalized, the methodcontinues at step 922 where the module generates a consistency of use ofcertification rating of 5 (and/or a word rating of “informal”). If,however, the consistency of use of certificates is at least formalized,the method continues at step 923 where the module determines whether theconsistency of use of certificates is metric & reporting. As a furtherand/or alternative example, metric & reporting includes formal plusthere are negligible tracking variations.

If the consistency of use of certificates is not metric & reporting, themethod continues at step 924 where the module generates a consistency ofuse of certification rating of 10 (and/or a word rating of “formal”).If, however, the consistency of use of certificates is at least metric &reporting, the method continues at step 925 where the module determineswhether the consistency of use of certificates is improvement. As afurther and/or alternative example, improvement includes metric &reporting plus the situations of use are routinely reviewed in anorganized manner and the situations of use are regulated.

If the consistency of use of certificates is not improvement, the methodcontinues at step 926 where the module generates a consistency of use ofcertification rating of 15 (and/or a word rating of “metric &reporting”). If the consistency of use of certificates is improvement,the method continues at step 927 where the module generates aconsistency of use of certification rating of 20 (and/or a word ratingof “improvement”). Note that the numerical rating are example values andcould be other values. Further note that the number of level ofconsistency of use of certification rating may be more or less than thefive shown.

FIG. 138 is a logic diagram of an example of a module of FIG. 132generating a consistency of use of automation evaluation rating. Themethod begins at step 928 where the module determines whether there isavailable automation for a particular system aspect, system criteria,system features, and/or system mode. If use of automation is notavailable, the method continues at step 929 where the module generatesan automation rating of 10 (and/or a word rating of “unavailable”).

If use of automation is available (e.g., there is automation for one ormore particular system features), the method continues at step 930 wherethe module determines whether there is at least one consistency of useof automation in the data. If not, the method continues at step 931where the module generates a consistency of use of automation rating of0 (and/or a word rating of “none”).

If there is at least one consistency of use of automation, the methodcontinues at step 932 where the module determines whether there was fullconsistency of use of automation in the data. As a further and/oralternative example, full consistency of use of automation refers to thesituations of use of automation is at an expected level.

If the consistency of use of automation is not full, the methodcontinues at step 933 where the module generates a consistency of use ofautomation rating of 5 (and/or a word rating of “partial”). If, however,the consistency of use of automation is full, the method continues atstep 934 where the module generates a consistency of use of automationrating of 10 (and/or a word rating of “full”). Note that the numericalrating are example values and could be other values. Further note thatthe number of level of use of automation may be more or less than thefour shown.

FIG. 139 is a logic diagram of an example of an analysis systemgenerating an evaluation output regrading processes of the system, orportion thereof. The method begins at step 935 where an analysis unit ofthe analysis system obtains (e.g., receives, gathers, inputs, and/orother means) a collection of data regarding processes of a system aspect(e.g., what is being evaluated with respect to one or more systemelements, one or more system criteria, and/or one or more system modes).

The method continues at step 936 where the analysis unit acquires (e.g.,receives, generates, determines, and/or other means) data analysisparameters regarding processes of the system aspect. An example of dataanalysis parameters were discussed with reference to FIG. 35 and withreference to one or more of 89-138.

The method continues at step 937 where the analysis unit determines oneor more evaluation perspectives based on the data analysis parameters.An evaluation perspective is understanding (e.g., knowledge and/orintent of system), implementation (e.g., how the system was developed),operation (e.g., how the system fulfills its objectives), orself-analysis (e.g., the system's self-protecting, self-healing, etc.).

The method continues at step 938 where the analysis unit determines oneor more evaluation modalities based on the data analysis parameters. Anevaluation modality is sufficiency, effectiveness, a measure of use, ameasure of appropriate of use, or a measure of consistency of use.Sufficiency is regarding an adequate quantity of data regardingprocesses associated with the system aspect. Effectiveness is regardingadequate content of the data regarding processes with respect to one ormore objectives of the system aspect. The measure of use is regardingthe quantity of use of the data regarding processes with respect tosupporting the one or more objectives of the system aspect. The measureof appropriate use is regarding the conditions of use of the dataregarding processes with respect to supporting the one or moreobjectives of the system aspect. The measure of consistency of use isregarding the situations of use of data regarding processes with respectto supporting the one or more objectives of the system aspect.

The method continues at step 940 where the analysis unit evaluates thecollection of data in accordance with processes, the one or moreevaluation perspectives, and the one or more evaluation modalities toproduce one or more evaluation outputs regarding processes. Anevaluation output is one or more evaluation ratings, one or more systemaspect deficiencies, or one or more auto-corrections of the one or moresystem aspect deficiencies.

FIG. 140 is a logic diagram of an example of an analysis systemgenerating an evaluation output regrading policies of the system, orportion thereof. The method begins at step 941 where an analysis unit ofthe analysis system obtains (e.g., receives, gathers, inputs, and/orother means) a collection of data regarding policies of a system aspect(e.g., what is being evaluated with respect to one or more systemelements, one or more system criteria, and/or one or more system modes).

The method continues at step 942 where the analysis unit acquires (e.g.,receives, generates, determines, and/or other means) data analysisparameters regarding policies of the system aspect. An example of dataanalysis parameters were discussed with reference to FIG. 35 and withreference to one or more of 89-138.

The method continues at step 943 where the analysis unit determines oneor more evaluation perspectives based on the data analysis pammeters. Anevaluation perspective is understanding (e.g., knowledge and/or intentof system), implementation (e.g., how the system was developed),operation (e.g., how the system fulfills its objectives), orself-analysis (e.g., the system's self-protecting, self-healing, etc.).

The method continues at step 944 where the analysis unit determines oneor more evaluation modalities based on the data analysis parameters. Anevaluation modality is sufficiency, effectiveness, a measure of use, ameasure of appropriate of use, or a measure of consistency of use.Sufficiency is regarding an adequate quantity of data regarding policiesassociated with the system aspect. Effectiveness is regarding adequatecontent of the data regarding policies with respect to one or moreobjectives of the system aspect. The measure of use is regarding thequantity of use of the data regarding policies with respect tosupporting the one or more objectives of the system aspect. The measureof appropriate use is regarding the conditions of use of the dataregarding policies with respect to supporting the one or more objectivesof the system aspect. The measure of consistency of use is regarding thesituations of use of data regarding policies with respect to supportingthe one or more objectives of the system aspect.

The method continues at step 946 where the analysis unit evaluates thecollection of data in accordance with policies, the one or moreevaluation perspectives, and the one or more evaluation modalities toproduce one or more evaluation outputs regarding policies. An evaluationoutput is one or more evaluation ratings, one or more system aspectdeficiencies, or one or more auto-corrections of the one or more systemaspect deficiencies.

FIG. 141 is a logic diagram of an example of an analysis systemgenerating an evaluation output regrading automation of the system, orportion thereof. The method begins at step 947 where an analysis unit ofthe analysis system obtains (e.g., receives, gathers, inputs, and/orother means) a collection of data regarding automation of a systemaspect (e.g., what is being evaluated with respect to one or more systemelements, one or more system criteria, and/or one or more system modes).

The method continues at step 948 where the analysis unit acquires (e.g.,receives, generates, determines, and/or other means) data analysisparameters regarding automation of the system aspect. An example of dataanalysis parameters were discussed with reference to FIG. 35 and withreference to one or more of 89-138.

The method continues at step 949 where the analysis unit determines oneor more evaluation perspectives based on the data analysis parmeters. Anevaluation perspective is understanding (e.g., knowledge and/or intentof system), implementation (e.g., how the system was developed),operation (e.g., how the system fulfills its objectives), orself-analysis (e.g., the system's self-protecting, self-healing, etc.).

The method continues at step 950 where the analysis unit determines oneor more evaluation modalities based on the data analysis parameters. Anevaluation modality is sufficiency, effectiveness, a measure of use, ameasure of appropriate of use, or a measure of consistency of use.Sufficiency is regarding an adequate quantity of data for automationassociated with the system aspect. Effectiveness is regarding adequatecontent of the data regarding automation with respect to one or moreobjectives of the system aspect. The measure of use is regarding thequantity of use of the data regarding automation with respect tosupporting the one or more objectives of the system aspect. The measureof appropriate use is regarding the conditions of use of the dataregarding automation with respect to supporting the one or moreobjectives of the system aspect. The measure of consistency of use isregarding the situations of use of data regarding automation withrespect to supporting the one or more objectives of the system aspect.

The method continues at step 952 where the analysis unit evaluates thecollection of data in accordance with automation, the one or moreevaluation perspectives, and the one or more evaluation modalities toproduce one or more evaluation outputs regarding automation. Anevaluation output is one or more evaluation ratings, one or more systemaspect deficiencies, or one or more auto-corrections of the one or moresystem aspect deficiencies.

FIG. 142 is a logic diagram of an example of an analysis systemgenerating an evaluation output regrading documentation of the system,or portion thereof. The method begins at step 953 where an analysis unitof the analysis system obtains (e.g., receives, gathers, inputs, and/orother means) a collection of data regarding documentation of a systemaspect (e.g., what is being evaluated with respect to one or more systemelements, one or more system criteria, and/or one or more system modes).

The method continues at step 954 where the analysis unit acquires (e.g.,receives, generates, determines, and/or other means) data analysisparameters regarding documentation of the system aspect. An example ofdata analysis parameters were discussed with reference to FIG. 35 andwith reference to one or more of 89-138.

The method continues at step 955 where the analysis unit determines oneor more evaluation perspectives based on the data analysis parameters.An evaluation perspective is understanding (e.g., knowledge and/orintent of system), implementation (e.g., how the system was developed),operation (e.g., how the system fulfills its objectives), orself-analysis (e.g., the system's self-protecting, self-healing, etc.).

The method continues at step 956 where the analysis unit determines oneor more evaluation modalities based on the data analysis parameters. Anevaluation modality is sufficiency, effectiveness, a measure of use, ameasure of appropriate of use, or a measure of consistency of use.Sufficiency is regarding an adequate quantity of data for documentationassociated with the system aspect. Effectiveness is regarding adequatecontent of the data regarding documentation with respect to one or moreobjectives of the system aspect. The measure of use is regarding thequantity of use of the data regarding documentation with respect tosupporting the one or more objectives of the system aspect. The measureof appropriate use is regarding the conditions of use of the dataregarding documentation with respect to supporting the one or moreobjectives of the system aspect. The measure of consistency of use isregarding the situations of use of data regarding documentation withrespect to supporting the one or more objectives of the system aspect.

The method continues at step 958 where the analysis unit evaluates thecollection of data in accordance with documentation, the one or moreevaluation perspectives, and the one or more evaluation modalities toproduce one or more evaluation outputs regarding documentation. Anevaluation output is one or more evaluation ratings, one or more systemaspect deficiencies, or one or more auto-corrections of the one or moresystem aspect deficiencies.

It is noted that terminologies as may be used herein such as bit stream,stream, signal sequence, etc. (or their equivalents) have been usedinterchangeably to describe digital information whose contentcorresponds to any of a number of desired types (e.g., data, video,speech, text, graphics, audio, etc. any of which may generally bereferred to as ‘data’).

As may be used herein, the terms “substantially” and “approximately”provide an industry-accepted tolerance for its corresponding term and/orrelativity between items. For some industries, an industry-acceptedtolerance is less than one percent and, for other industries, theindustry-accepted tolerance is 10 percent or more. Other examples ofindustry-accepted tolerance range from less than one percent to fiftypercent. Industry-accepted tolerances correspond to, but are not limitedto, component values, integrated circuit process variations, temperaturevariations, rise and fall times, thermal noise, dimensions, signalingerrors, dropped packets, temperatures, pressures, material compositions,and/or performance metrics. Within an industry, tolerance variances ofaccepted tolerances may be more or less than a percentage level (e.g.,dimension tolerance of less than +/−1%). Some relativity between itemsmay range from a difference of less than a percentage level to a fewpercent. Other relativity between items may range from a difference of afew percent to magnitude of differences.

As may also be used herein, the term(s) “configured to”, “operablycoupled to”, “coupled to”, and/or “coupling” includes direct couplingbetween items and/or indirect coupling between items via an interveningitem (e.g., an item includes, but is not limited to, a component, anelement, a circuit, and/or a module) where, for an example of indirectcoupling, the intervening item does not modify the information of asignal but may adjust its current level, voltage level, and/or powerlevel. As may further be used herein, inferred coupling (i.e., where oneelement is coupled to another element by inference) includes direct andindirect coupling between two items in the same manner as “coupled to”.

As may even further be used herein, the term “configured to”, “operableto”, “coupled to”, or “operably coupled to” indicates that an itemincludes one or more of power connections, input(s), output(s), etc., toperform, when activated, one or more its corresponding functions and mayfurther include inferred coupling to one or more other items. As maystill further be used herein, the term “associated with”, includesdirect and/or indirect coupling of separate items and/or one item beingembedded within another item.

As may be used herein, the term “compares favorably”, indicates that acomparison between two or more items, signals, etc., provides a desiredrelationship. For example, when the desired relationship is that signal1 has a greater magnitude than signal 2, a favorable comparison may beachieved when the magnitude of signal 1 is greater than that of signal 2or when the magnitude of signal 2 is less than that of signal 1. As maybe used herein, the term “compares unfavorably”, indicates that acomparison between two or more items, signals, etc., fails to providethe desired relationship.

As may be used herein, one or more claims may include, in a specificform of this generic form, the phrase “at least one of a, b, and c” orof this generic form “at least one of a, b, or c”, with more or lesselements than “a”, “b”, and “c”. In either phrasing, the phrases are tobe interpreted identically. In particular, “at least one of a, b, and c”is equivalent to “at least one of a, b, or c” and shall mean a, b,and/or c. As an example, it means: “a” only, “b” only, “c” only, “a” and“b”, “a” and “c”, “b” and “c”, and/or “a”, “b”, and “c”.

As may also be used herein, the terms “processing module”, “processingcircuit”, “processor”, “processing circuitry”, and/or “processing unit”may be a single processing device or a plurality of processing devices.Such a processing device may be a microprocessor, micro-controller,digital signal processor, microcomputer, central processing unit, fieldprogrammable gate array, programmable logic device, state machine, logiccircuitry, analog circuitry, digital circuitry, and/or any device thatmanipulates signals (analog and/or digital) based on hard coding of thecircuitry and/or operational instructions. The processing module,module, processing circuit, processing circuitry, and/or processing unitmay be, or further include, memory and/or an integrated memory element,which may be a single memory device, a plurality of memory devices,and/or embedded circuitry of another processing module, module,processing circuit, processing circuitry, and/or processing unit. Such amemory device may be a read-only memory, random access memory, volatilememory, non-volatile memory, static memory, dynamic memory, flashmemory, cache memory, and/or any device that stores digital information.Note that if the processing module, module, processing circuit,processing circuitry, and/or processing unit includes more than oneprocessing device, the processing devices may be centrally located(e.g., directly coupled together via a wired and/or wireless busstructure) or may be distributedly located (e.g., cloud computing viaindirect coupling via a local area network and/or a wide area network).Further note that if the processing module, module, processing circuit,processing circuitry and/or processing unit implements one or more ofits functions via a state machine, analog circuitry, digital circuitry,and/or logic circuitry, the memory and/or memory element storing thecorresponding operational instructions may be embedded within, orexternal to, the circuitry comprising the state machine, analogcircuitry, digital circuitry, and/or logic circuitry. Still further notethat, the memory element may store, and the processing module, module,processing circuit, processing circuitry and/or processing unitexecutes, hard coded and/or operational instructions corresponding to atleast some of the steps and/or functions illustrated in one or more ofthe Figures. Such a memory device or memory element can be included inan article of manufacture.

One or more embodiments have been described above with the aid of methodsteps illustrating the performance of specified functions andrelationships thereof. The boundaries and sequence of these functionalbuilding blocks and method steps have been arbitrarily defined hereinfor convenience of description. Alternate boundaries and sequences canbe defined so long as the specified functions and relationships areappropriately performed. Any such alternate boundaries or sequences arethus within the scope and spirit of the claims. Further, the boundariesof these functional building blocks have been arbitrarily defined forconvenience of description. Alternate boundaries could be defined aslong as the certain significant functions are appropriately performed.Similarly, flow diagram blocks may also have been arbitrarily definedherein to illustrate certain significant functionality.

To the extent used, the flow diagram block boundaries and sequence couldhave been defined otherwise and still perform the certain significantfunctionality. Such alternate definitions of both functional buildingblocks and flow diagram blocks and sequences are thus within the scopeand spirit of the claims One of average skill in the art will alsorecognize that the functional building blocks, and other illustrativeblocks, modules and components herein, can be implemented as illustratedor by discrete components, application specific integrated circuits,processors executing appropriate software and the like or anycombination thereof.

In addition, a flow diagram may include a “start” and/or “continue”indication. The “start” and “continue” indications reflect that thesteps presented can optionally be incorporated in or otherwise used inconjunction with one or more other routines. In addition, a flow diagrammay include an “end” and/or “continue” indication. The “end” and/or“continue” indications reflect that the steps presented can end asdescribed and shown or optionally be incorporated in or otherwise usedin conjunction with one or more other routines. In this context, “start”indicates the beginning of the first step presented and may be precededby other activities not specifically shown. Further, the “continue”indication reflects that the steps presented may be performed multipletimes and/or may be succeeded by other activities not specificallyshown. Further, while a flow diagram indicates a particular ordering ofsteps, other orderings are likewise possible provided that theprinciples of causality are maintained.

The one or more embodiments are used herein to illustrate one or moreaspects, one or more features, one or more concepts, and/or one or moreexamples. A physical embodiment of an apparatus, an article ofmanufacture, a machine, and/or of a process may include one or more ofthe aspects, features, concepts, examples, etc. described with referenceto one or more of the embodiments discussed herein. Further, from figureto figure, the embodiments may incorporate the same or similarly namedfunctions, steps, modules, etc. that may use the same or differentreference numbers and, as such, the functions, steps, modules, etc. maybe the same or similar functions, steps, modules, etc. or differentones.

While the transistors in the above described figure(s) is/are shown asfield effect transistors (FETs), as one of ordinary skill in the artwill appreciate, the transistors may be implemented using any type oftransistor structure including, but not limited to, bipolar, metal oxidesemiconductor field effect transistors (MOSFET), N-well transistors,P-well transistors, enhancement mode, depletion mode, and zero voltagethreshold (VT) transistors.

Unless specifically stated to the contra, signals to, from, and/orbetween elements in a figure of any of the figures presented herein maybe analog or digital, continuous time or discrete time, and single-endedor differential. For instance, if a signal path is shown as asingle-ended path, it also represents a differential signal path.Similarly, if a signal path is shown as a differential path, it alsorepresents a single-ended signal path. While one or more particulararchitectures are described herein, other architectures can likewise beimplemented that use one or more data buses not expressly shown, directconnectivity between elements, and/or indirect coupling between otherelements as recognized by one of average skill in the art.

The term “module” is used in the description of one or more of theembodiments. A module implements one or more functions via a device suchas a processor or other processing device or other hardware that mayinclude or operate in association with a memory that stores operationalinstructions. A module may operate independently and/or in conjunctionwith software and/or firmware. As also used herein, a module may containone or more sub-modules, each of which may be one or more modules.

As may further be used herein, a computer readable memory includes oneor more memory elements. A memory element may be a separate memorydevice, multiple memory devices, or a set of memory locations within amemory device. Such a memory device may be a read-only memory, randomaccess memory, volatile memory, non-volatile memory, static memory,dynamic memory, flash memory, cache memory, and/or any device thatstores digital information. The memory device may be in a form asolid-state memory, a hard drive memory, cloud memory, thumb drive,server memory, computing device memory, and/or other physical medium forstoring digital information.

While particular combinations of various functions and features of theone or more embodiments have been expressly described herein, othercombinations of these features and functions are likewise possible. Thepresent disclosure is not limited by the particular examples disclosedherein and expressly incorporates these other combinations.

What is claimed is:
 1. A method comprises: obtaining, by an analysisunit of an analysis system that includes one or more computing entities,a collection of data for an evaluation of documentation of a systemaspect of a system; acquiring, by the analysis unit, data analysisparameters regarding the evaluation of the documentation of the systemaspect; determining, by the analysis unit, one or more evaluationperspectives based on the data analysis parameters; determining, by theanalysis unit, one or more evaluation modalities based on the dataanalysis parameters; and evaluating, by the analysis unit, thecollection of data with respect to the documentation of the systemaspect based on the one or more evaluation perspectives and the one ormore evaluation modalities to produce one or more evaluation outputsregarding the documentation of the system aspect.
 2. The method of claim1, wherein the system aspect comprises: one or more system elements; oneor more system criteria; and/or one or more system modes.
 3. The methodof claim 1, wherein an evaluation perspective of the one or moreevaluation perspectives comprises: understanding; implementation;operation; or self-analysis.
 4. The method of claim 1, wherein anevaluation modality of the one or more evaluation modalities comprises:a level of sufficiency of an evaluation metric of the one or moreevaluation metrics associated with the system aspect; a level ofeffectiveness of the evaluation metric with respect to one or moreobjectives of the system aspect; a measure of use of the evaluationmetric with respect to supporting the one or more objectives of thesystem aspect; a measure of appropriate use of the evaluation metricwith respect to supporting the one or more objectives of the systemaspect; or a measure of consistency of use of the evaluation metric withrespect to supporting the one or more objectives of the system aspect.5. The method of claim 1, wherein an evaluation output of the one ormore evaluation outputs comprises: one or more evaluation ratings; oneor more system aspect deficiencies; or one or more auto-corrections ofthe one or more system aspect deficiencies.
 6. The method of claim 1,wherein the evaluating the collection of data comprises: when the one ormore evaluation modalities is a sufficiency modality: quantifying dataof the collection of data regarding the documentation of the systemaspect to produce quantified data; determining a reference scale basedon an evaluation perspective of the one or more evaluation perspectivesand one or more objectives of the system aspect for the evaluationmetric; and comparing the quantified data with the reference scale toproduce an evaluation rating regarding sufficiency of the documentationof the system aspect from the evaluation perspective.
 7. The method ofclaim 1, wherein the evaluating the collection of data comprises: whenthe one or more evaluation modalities is an effectiveness modality:determining a reference scale based on an evaluation perspective of theone or more evaluation perspectives and one or more objectives of thesystem aspect for the documentation of the system aspect; and evaluatingdata of the collection of data regarding the documentation of the systemaspect with respect to the reference scale to produce an evaluationrating regarding how effective the documentation of the system aspectsupport the one or more objectives of the system aspect from theevaluation perspective.
 8. The method of claim 1, wherein the evaluatingthe collection of data comprises: when the one or more evaluationmodalities is a measure of use modality: determining a reference scalebased on an evaluation perspective of the one or more evaluationperspectives and one or more objectives of the system aspect for thedocumentation of the system aspect; and evaluating data of thecollection of data regarding the documentation of the system aspect withrespect to the reference scale to produce an evaluation rating regardinguse of the documentation of the system aspect to support the one or moreobjectives of the system aspect from the evaluation perspective.
 9. Themethod of claim 1, wherein the evaluating the collection of datacomprises: when the one or more evaluation modalities is a measure ofappropriate use modality: determining a reference scale based on anevaluation perspective of the one or more evaluation perspectives andone or more objectives of the system aspect for the documentation of thesystem aspect; and evaluating data of the collection of data regardingthe documentation of the system aspect with respect to the referencescale to produce an evaluation rating regarding appropriate use of thedocumentation of the system aspect to support the one or more objectivesof the system aspect from the evaluation perspective.
 10. The method ofclaim 1, wherein the evaluating the collection of data comprises: whenthe one or more evaluation modalities is a measure of consistency of usemodality: determining a reference scale based on an evaluationperspective of the one or more evaluation perspectives and one or moreobjectives of the system aspect for the documentation of the systemaspect; and evaluating data of the collection of data regarding thedocumentation of the system aspect with respect to the reference scaleto produce an evaluation rating regarding consistency of use of thedocumentation of the system aspect to support the one or more objectivesof the system aspect from the evaluation perspective.
 11. The method ofclaim 1 further comprises: determining, by the analysis unit, one ormore evaluation viewpoints based on the data analysis parameters. 12.The method of claim 11, wherein an evaluation viewpoint of the one ormore evaluation viewpoints comprises: a disclosed data viewpoint; adiscovered data viewpoint; or a desired data viewpoint.
 13. The methodof claim 1 further comprises: determining, by the analysis unit, one ormore evaluation categories based on the data analysis parameters. 14.The method of claim 13, wherein an evaluation category of the one ormore evaluation categories comprises: an identify category; a protectcategory; a detect category; a respond category; or a recover category.15. The method of claim 1, wherein the documentation includes systemrequirements.
 16. The method of claim 1, wherein the documentationincludes system designs.
 17. The method of claim 1, wherein thedocumentation includes system operations.
 18. The method of claim 1,wherein the documentation includes system assets.
 19. The method ofclaim 1, wherein the documentation includes security requirements.
 20. Acomputer readable memory comprises: a non-transitory memory operable tostore operational instructions that, when executed by an analysis unitof analysis system that includes one or more computing entities, causesthe analysis unit to perform operations that include: obtaining, by ananalysis unit of an analysis system that includes one or more computingentities, a collection of data for an evaluation of documentation of asystem aspect of a system; acquiring, by the analysis unit, dataanalysis parameters regarding the evaluation of the documentation of thesystem aspect; determining, by the analysis unit, one or more evaluationperspectives based on the data analysis parameters; determining, by theanalysis unit, one or more evaluation modalities based on the dataanalysis parameters; and evaluating, by the analysis unit, thecollection of data with respect to the documentation of the systemaspect based on the one or more evaluation perspectives and the one ormore evaluation modalities to produce one or more evaluation outputsregarding the documentation of the system aspect.